[Issue 14885] ideas for prettier and more useful backtraces

via Digitalmars-d-bugs digitalmars-d-bugs at puremagic.com
Tue Sep 1 00:57:33 PDT 2015


https://issues.dlang.org/show_bug.cgi?id=14885

Vladimir Panteleev <thecybershadow at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thecybershadow at gmail.com

--- Comment #5 from Vladimir Panteleev <thecybershadow at gmail.com> ---
(In reply to Martin Nowak from comment #0)
> Turn backtraces upside down.
> Often one get's a long backtrace on the console and has to scroll up
> skipping all the internal/framework frames to find the actual function that
> threw an exception and see the error message.
> 
> It would be a lot easier if the backtrace was from top to bottom with the
> message below that.

That would go against existing conventions pretty much anywhere. Debuggers
(GDB, Visual Studio), as most other programming languages (Java, C#, Ruby) show
stack traces with the most recent call first. Python is an exception, which
explains why I always get confused when reading Python stack traces.

--


More information about the Digitalmars-d-bugs mailing list