From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6713 invoked by alias); 26 Mar 2008 12:06:45 -0000 Received: (qmail 6706 invoked by uid 22791); 26 Mar 2008 12:06:44 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 26 Mar 2008 12:06:16 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1JeUOS-0007DZ-W4; Wed, 26 Mar 2008 13:06:13 +0100 Subject: Re: common print-stack options From: Mark Wielaard To: Andrew Cagney Cc: frysk In-Reply-To: <47E2ADF7.50808@redhat.com> References: <47E2ADF7.50808@redhat.com> Content-Type: text/plain Date: Wed, 26 Mar 2008 12:06:00 -0000 Message-Id: <1206533172.3553.58.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00183.txt.bz2 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