On Tue, Mar 18, 2008 at 05:24:20PM -0700, Brian Dessent wrote:
>
>This patch adds the ability to see functions/symbols in the .stackdump
>files generated when there's a fault. It parses the export sections of
>each loaded module and finds the closest exported address for each stack
>frame address.
Igor Peshansky wrote:
> Would it make sense to force a newline before the function name and to
> display it with a small indent? That way people who want the old-style
> stackdump could just feed the new one into "grep -v '^ '" or something...
Yes, that would be one way. That actually reminds
On Tue, 18 Mar 2008, Brian Dessent wrote:
> Brian Dessent wrote:
>
> > Of course the labeling works for any module/dll, not just cygwin1.dll,
> > but I didn't have a more elaborate testcase to demonstrate.
>
> Forgot to mention...
>
> The symbols are just tacked on on the right hand side there for
Brian Dessent wrote:
> Of course the labeling works for any module/dll, not just cygwin1.dll,
> but I didn't have a more elaborate testcase to demonstrate.
Forgot to mention...
The symbols are just tacked on on the right hand side there for now. I
wasn't really sure how to handle that. I didn
This patch adds the ability to see functions/symbols in the .stackdump
files generated when there's a fault. It parses the export sections of
each loaded module and finds the closest exported address for each stack
frame address. This of course won't be perfect as it will show the
wrong function
