From: Sami Wagiaalla <swagiaal@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: fstack options
Date: Tue, 12 Jun 2007 21:56:00 -0000 [thread overview]
Message-ID: <466DB047.4030103@redhat.com> (raw)
In-Reply-To: <466D7775.20901@redhat.com>
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.
next prev parent reply other threads:[~2007-06-11 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 20:27 Sami Wagiaalla
2007-06-12 21:56 ` Sami Wagiaalla [this message]
2007-06-14 19:06 ` Andrew Cagney
2007-06-15 9:44 ` Mark Wielaard
2007-06-15 14:07 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466DB047.4030103@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).