Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Van Belle <Jan.Van_Belle@alcatel.be>
To: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: STEP and CONTINUE in GDB REMOTE
Date: Mon, 04 Nov 2002 06:52:00 -0000	[thread overview]
Message-ID: <3DC68A0A.7ABED424@alcatel.be> (raw)
In-Reply-To: <20021104144648.GA13511@nevyn.them.org>

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



  reply	other threads:[~2002-11-04 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  6:22 Jan Van Belle
2002-11-04  6:27 ` Daniel Jacobowitz
2002-11-04  6:36   ` Jan Van Belle
2002-11-04  6:46     ` Daniel Jacobowitz
2002-11-04  6:52       ` Jan Van Belle [this message]
2002-11-04  6:56         ` Daniel Jacobowitz
2002-11-04  6:59       ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DC68A0A.7ABED424@alcatel.be \
    --to=jan.van_belle@alcatel.be \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox