Re: Unfolding the stack

2012-03-12 Thread Ryan Johnson
On 12/03/2012 11:20 AM, Michel Bardiaux wrote: Alternatively, you could compile with -g and try to traverse the debug info tables gdb uses to work> around everything nasty gcc does, but there's no clean API there that I know of. Since cygwin_stackdump does not dare to tread there... Pretty muc

FW: Unfolding the stack

2012-03-12 Thread Michel Bardiaux
[snip] > This is hard in C, and harder in code compiled by gcc [snip] I know that, and am willing to accept the risk since any info is better than none. I just wish for a more efficient mechanism than I am now using. > If you're using C++, [snip] Nope. > Alternatively, you could compile with -g

Re: Unfolding the stack

2012-03-12 Thread Ryan Johnson
On 12/03/2012 5:39 AM, Michel Bardiaux wrote: To complete the port of some library to Cygwin, I need a way to produce a traceback with as much info as possible. Currently I have something that works but not that well. There are basically 3 parts: * Gather all the stack frames; see below. * Ass

Unfolding the stack

2012-03-12 Thread Michel Bardiaux
To complete the port of some library to Cygwin, I need a way to produce a traceback with as much info as possible. Currently I have something that works but not that well. There are basically 3 parts: * Gather all the stack frames; see below. * Assign the PCs in each frame to some executable imag