This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: fstack options
- From: Andrew Cagney <cagney at redhat dot com>
- To: Sami Wagiaalla <swagiaal at redhat dot com>
- Cc: frysk at sourceware dot org
- Date: Thu, 14 Jun 2007 13:51:50 -0400
- Subject: Re: fstack options
- References: <466D7775.20901@redhat.com> <466DB047.4030103@redhat.com>
fstack's, and its pre-cursors - gstack and pstack, first priority is
speed - get in, get a backtrace, get out - and I think it is fair to
assume that having to scan multi-megabytes of .debug info would run
against that goal (fstack probably shouldn't look in .debug_line by
default either).
Perhaps an option << fstack -a >> to reverse the goal and display
everything known about the function would address this.
Andrew
Sami Wagiaalla wrote:
Sami Wagiaalla wrote:
right now fstack prints a stack trace using only elf information.
Although this is still the default, personally I think the default
should be print function names and parameters if debuginfo is
available other wise fall back to elf symbol. And provide an option
for getting an elf only stack back trace.