This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: _Py_DumpTraceback should be PyAPI_FUNC
Type: Stage: resolved
Components: Interpreter Core Versions: Python 3.6
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: John.Malmberg, berker.peksag, serhiy.storchaka, vstinner
Priority: normal Keywords:

Created on 2016-01-14 13:10 by John.Malmberg, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg258199 - (view) Author: John Malmberg (John.Malmberg) * Date: 2016-01-14 13:10
The _PyDumpTraceback and _Py_DumpTracebackThreads routines in traceback.h are tagged with PyAPI_DATA attributes when they should be tagged with PyAPI_FUNC.

For platforms that use those attributes, this can cause run-time issues if those methods are called.
msg258201 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2016-01-14 14:21
Correction for searching: _Py_DumpTraceback and _Py_DumpTracebackThreads. They were added with the faulthandler module in issue11393.
msg271844 - (view) Author: Berker Peksag (berker.peksag) * (Python committer) Date: 2016-08-02 19:34
Thanks for the report. This has already been fixed in 4f5e4155c259 ( Python 3.5+)
History
Date User Action Args
2022-04-11 14:58:26adminsetgithub: 70297
2016-08-02 19:34:21berker.peksagsetstatus: open -> closed

nosy: + berker.peksag
messages: + msg271844

resolution: out of date
stage: resolved
2016-01-14 14:21:17serhiy.storchakasetnosy: + vstinner, serhiy.storchaka
messages: + msg258201
2016-01-14 13:10:34John.Malmbergcreate