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: using tracepoints function with both host and target on same computer


Daniel:


Er, I guess you were clear on that, weren't you?  My bad.

b.g.

On Wed, Aug 07, 2002 at 11:23:46AM -0400, Daniel Jacobowitz wrote:
> On Wed, Aug 07, 2002 at 10:21:13AM -0500, William A. Gatliff wrote:
> > Daniel:
> > 
> > 
> > On Wed, Aug 07, 2002 at 11:01:50AM -0400, Daniel Jacobowitz wrote:
> > > You don't do them in actual realtime, but neither do you wait for all
> > > of GDB to process the event; you receive the breakpoint, collect
> > > tracepoint data, and immediately resume without touching GDB's event
> > > loop.  It's a little slower than an in-application stub because it has
> > > to use ptrace to read memory/registers, but not substantially slower.
> > 
> > ... except that I don't think you'd want to be doing that across a
> > 9600bps remote link.  Or, you'd at least want to have the option not
> > to.
> 
> I was talking about the native case.  If you have a stub, you do it in
> the stub.  You do it wherever a trap is handled; in native that's GDB
> itself, otherwise it's gdbserver or your target stub.
> 
> 
> -- 
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer

-- 
Bill Gatliff
bgat@billgatliff.com


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