[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: STEP and CONTINUE in GDB REMOTE
From:       Jan Van Belle <Jan.Van_Belle () alcatel ! be>
Date:       2002-11-04 14:54:02
Message-ID: 3DC68A0A.7ABED424 () alcatel ! be
[Download RAW message or body]

Daniel Jacobowitz wrote:

> >
> > Yes I have. I have a copy printed out on my desk. This document explains us
> > which possible responses there are,
> > but not when to send which one, and certainly not what the contents should be
> > for
> >
> > TAAn...:r...;n...:r...;n...:r...;
> >
> > I already did several Google's for this topic, but I guess I'll have to find
> > it in someone's private collection
>
> The explanation of T isn't the clearest...
>
> SAA: stop with signal AA
> TAA: stop with signal AA, and return the values of registers that we
>      know will be queried, or other information:
>
> n... = register number (hex), r... = target byte ordered register
> contents, size defined by REGISTER_RAW_SIZE;
>
> n... = `thread', r... = thread process ID, this is a hex integer;
>
> n... = (`watch' | `rwatch' | `awatch', r... = data address, this is a hex integer;
>
> n... = other string not starting with valid hex digit. GDB should ignore this n...,
> r... pair and go on to the next.
>
> NAA is obsolete and Oxx is... frowned upon.
>

Aha, now we're talking
Maybe this could be added in the manual (hint hint)

Thanks a lot !!

Regards,

Jan


[prev in list] [next in list] [prev in thread] [next in thread]