The "new" stack trace format
Wed May 17 19:54:00 GMT 2000
As you probably all know, DJ implemented a new stack trace format for
cygwin several months ago.
I just wanted to express my appreciation for this new format as it helped
me track down a problem that I was having which was hard to reproduce
when running under gdb.
The layout is a lot easier to visually decode than the previous version
and I realized that after looking at five or six stackdumps.
Of course, I thought there was a problem with the code that was walking
the stack since the same addresses seemed to be repeating in the "Function"
column but, of course, duh, the problem was that one of cygwin's functions
was being called recursively, erroneously.
More information about the Cygwin-developers