From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: common print-stack options
Date: Wed, 26 Mar 2008 12:06:00 -0000 [thread overview]
Message-ID: <1206533172.3553.58.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <47E2ADF7.50808@redhat.com>
Hi Andrew,
On Thu, 2008-03-20 at 14:33 -0400, Andrew Cagney wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=5978
>
> FYI, all the utilities (fstack, ftrace, ferror, fcatch) now share a
> common set of options for specifying what a stack backtrace should look
> like, for instance:
>
> I've marked down a brainstorming session on what the print-stack options
> should be for next wednesday's meeting.
I think the suggested options in the bug report are nice:
Stack print options:
-n, -number-of-frames NUMBER number of frames to print. Use -n 0 or -n
all to print all frames.
-f, -full-path print the full path to object files
-a, -all Print all information that can be retrieved
about the stack
this is equivalent to -print
functions,params,scopes,fullpath
-v, -virtual Includes virtual frames in the stack trace.
Virtual frames are artificial frames
corresponding to calls to inlined functions
-c, -common print commonly used debug information:this
is equivalent to -print
functions,params,fullpath
-print [item],... itmes to print. Possible items:
functions : print function names using
debug information
scopes : print variables declared in each
scope within the function.
params : print function parameters
fullpath : print full executbale path
Having some options separate and available also in --print [item] is
slightly confusing though, I would propose to make them all "top-level"
options, or all --print [item] options.
Since this is a common option but just for stack trace printing, you
might want to change --print [item] to --stack [item]. Where a --stack
without items replaces the --common option. And maybe replace -a with
--stack all.
Cheers,
Mark
prev parent reply other threads:[~2008-03-26 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 18:34 Andrew Cagney
2008-03-26 12:06 ` Mark Wielaard [this message]
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=1206533172.3553.58.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@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).