[issue14665] faulthandler prints tracebacks in reverse order

Nick Coghlan added the comment: For additional context, Guido's patch in issue 19306 changed "Traceback" to "Stack" and added the "(most recent call first)" to some places where it was missing. Given the technical arguments in favour of keeping this code as simple as possible, agreed this is

[issue14665] faulthandler prints tracebacks in reverse order

STINNER Victor added the comment: The issue #19306 changed faulthandler output to mention explicitly the frame order. I'm still opposed to reverse_frames.patch for the reason I gave above. Can I close this issue as "wont fix"? -- ___ Python tracker

[issue14665] faulthandler prints tracebacks in reverse order

Changes by Yury Selivanov : -- versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue14665] faulthandler prints tracebacks in reverse order

STINNER Victor added the comment: > Victor's argument makes sense to me. What I'd be inclined to do is shout at > the reader a bit in the traceback header by making it: > >    Traceback (most recent call FIRST): The output is something like: Thread 0xf758d8d0: File "/home/edcjones/programs/

[issue14665] faulthandler prints tracebacks in reverse order

Nick Coghlan added the comment: Victor's argument makes sense to me. What I'd be inclined to do is shout at the reader a bit in the traceback header by making it: Traceback (most recent call FIRST): And put a comment in the source code with the gist of what Victor wrote above (i.e. inter

[issue14665] faulthandler prints tracebacks in reverse order

STINNER Victor added the comment: faulthandler has to be as simple as possible because Python internal state may be completly corrupted. faulthandler was written to display the traceback on bugs like invalid memory read or write. I chose to print the traceback as it is stored in memory (from

[issue14665] faulthandler prints tracebacks in reverse order

Antoine Pitrou added the comment: Here is a patch. -- keywords: +patch nosy: +ncoghlan Added file: http://bugs.python.org/file25355/reverse_frames.patch ___ Python tracker ___ _

[issue14665] faulthandler prints tracebacks in reverse order

New submission from Antoine Pitrou : Python usually prints traceback from the outer to the inner function: the inner frame is printed last. But faulthandler prints the inner frame first and the outer frame last. -- components: Extension Modules messages: 159223 nosy: haypo, pitrou prio