This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: new option --readnever & script gstack?


On Mon, Nov 29, 2004 at 11:11:37AM -0500, Daniel Jacobowitz wrote:
> On Mon, Nov 29, 2004 at 11:07:06AM -0500, Andrew Cagney wrote:
> > Yes, the objective is to get in, get a minimal backtrace, and get out. 
> > Apparently this is a relatively common task in production environments - 
> >  a few seconds down time is considered acceptable but not a few minutes 
> > (that's the magnitude difference I'm seeing :-/).  I also don't see the 
> > option as being pstack specific - this technique is equally applicable 
> > to other scripts - gcore comes to mind - again only minimal symbol 
> > information being required.
> > 
> > So, ..., would a gstack.sh script and an option to disable symbolic 
> > debug information reading be useful additions to GDB?

Oh, two other things.  I liked Frank's suggestion:

  Or alternately, could the "asneeded" setting stay as it is, but extend
  gdb's backtrace command to have a sufficiently non-symbolic mode,
  where the "asneeded" data would not be needed and thus not loaded?

And I don't think we need a command line option for this.  Would a
"set" be enough?  You're going to have to feed a command file to GDB
anyway to get the backtrace.

-- 
Daniel Jacobowitz


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]