|
Archives
D Programming
DD.gnu digitalmars.D digitalmars.D.bugs digitalmars.D.dtl digitalmars.D.ide digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript electronics |
digitalmars.D.debugger - [ddbg] Stack trace output format
Just a suggestion, but I find it is often fairly difficult to locate the file and line numbers in the stack traces ddbg spits out. On a standard-width terminal the lines get wrapped around so much that generally the filename is split across a newline boundary. Something to make the file and line numbers stand out more would be nice. Just writing the filename and line number on a line by themselves would probably help a lot. Or perhaps a ddbg flag to turn on some fancy ANSI escape sequences to make the important bits appear in bold/red/blink mode or something. It doesn't really matter to me as long as they become easier to read. --bb May 16 2008
Bill Baxter wrote:Just a suggestion, but I find it is often fairly difficult to locate the file and line numbers in the stack traces ddbg spits out. On a standard-width terminal the lines get wrapped around so much that generally the filename is split across a newline boundary. Something to make the file and line numbers stand out more would be nice. Just writing the filename and line number on a line by themselves would probably help a lot. Or perhaps a ddbg flag to turn on some fancy ANSI escape sequences to make the important bits appear in bold/red/blink mode or something. It doesn't really matter to me as long as they become easier to read. --bb Jun 29 2008
|