This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Thread awareness in remote serial protocol Z packet
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Earl Chew <earl_chew at agilent dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 11 Sep 2002 13:54:51 -0400
- Subject: Re: Thread awareness in remote serial protocol Z packet
- References: <3D7F7923.B504AA7D@agilent.com>
On Wed, Sep 11, 2002 at 10:10:59AM -0700, Earl Chew wrote:
> I'm implementing a remote serial protocol agent. The target
> supports global and thread specific breakpoints.
>
> Reading the documentation for Zt,addr,length and browsing
> breakpoint_thread_match() and insert_breakpoints() in
> gdb/breakpoint.c (gdb 5.0) suggests that gdb can only cause the
> remote to insert global breakpoints, then check after the
> breakpoint is reached as to which thread caused the break.
>
> Is this correct?
I believe so.
> Under some circumstances it would be advantageous to have
> the remote filter the breakpoints to avoid many false
> stop/starts.
>
> Perhaps extended the Z protocol to allow Zt,addr,length,id
> (plus the corresponding change in breakpoint.c) would be sufficient
> to allow this. Old targets presumably would ignore the ,id
> argument and proceed as before.
Either that or we'd need to specify a different packet type for this...
gdbserver doesn't support the Z packet right now, so it wouldn't care;
it could easily be extended to support the Z packet and to support
thread-specific breakpoints but I haven't had a chance.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer