Skip to content

gh-145559: Make PyUnstable_DumpTraceback return void again #154131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hoodmane wants to merge 1 commit into from
Closed

gh-145559: Make PyUnstable_DumpTraceback return void again #154131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions Python/traceback.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1167,11 +1167,10 @@

The caller is responsible to call PyErr_CheckSignals() to call Python signal
handlers if signals were received. */
const char*
void
PyUnstable_DumpTraceback(int fd, PyThreadState *tstate)

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows / Build and test (x64, switch-case) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows / Build and test (x64, tail-call) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows (free-threading) / Build and test (x64, tail-call) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows (free-threading) / Build and test (x64, switch-case) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Hypothesis tests on Ubuntu 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Ubuntu / build and test (ubuntu-26.04-arm) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows / Build and test (arm64, switch-case) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Ubuntu (free-threading) / build and test (ubuntu-26.04) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Ubuntu (bolt) / build and test (ubuntu-26.04) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Cross build Linux 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Ubuntu / build and test (ubuntu-26.04) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Ubuntu (free-threading) / build and test (ubuntu-26.04-arm) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Windows (free-threading) / Build and test (arm64, switch-case) 

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Check failure on line 1171 in Python/traceback.c

View workflow job for this annotation

GitHub Actions / Address sanitizer (ubuntu-26.04) 

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int,  PyThreadState *)’ {aka ‘void(int,  struct _ts *)’}
{
dump_traceback(fd, tstate, 1);
return NULL;
}

#if defined(HAVE_PTHREAD_GETNAME_NP) || defined(HAVE_PTHREAD_GET_NAME_NP)
Expand Down
Loading