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: Thread signal information


Calling functions in the live program, from the GDB prompt, while
debugging it.

On Thu, Jul 25, 2002 at 08:59:35AM -0700, Lucy Zhang wrote:
> What are inferior function calls?
> 
> Lucy
> ----- Original Message -----
> From: "Dan Kegel" <dkegel@ixiacom.com>
> To: "Daniel Jacobowitz" <drow@mvista.com>
> Cc: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>; <gdb@sources.redhat.com>
> Sent: Wednesday, July 24, 2002 12:53 PM
> Subject: Re: Thread signal information
> 
> 
> > Daniel Jacobowitz wrote:
> > >>Does one give up anything by doing a postmortem gdb session
> > >>rather than a live session?
> > >
> > > From a design perspective, in the corefiles we get each thread's
> > > registers from the kernel; in live debugging we use thread_db.
> > > Given Linux's one-process-one-thread model at present, this has no
> > > practical significance.
> >
> > ... but it might if/when people start using NGPT instead of LinuxThreads.
> > I suppose I should check to see what that project plans to do about core
> dumps.
> >
> > > From a convenience perspective, as Andrew said, you lose inferior
> > > function calls.  You can't modify memory.  Etc.
> >
> > Thanks!
> > - Dan
> >
> >
> 
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


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