Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Johns <chrisj@rtems.org>
To: Chris Johns <chrisj@rtems.org>, gdb-patches@sourceware.org
Subject: Re: gdbserver pipe, xml and monitor changes
Date: Tue, 06 Nov 2007 06:02:00 -0000	[thread overview]
Message-ID: <47300364.3040000@rtems.org> (raw)
In-Reply-To: <20071106033408.GA18729@caradoc.them.org>

Daniel Jacobowitz wrote:
> 
> Take a look at the gdb Wiki; there's a page describing how to run the
> testsuite against a local gdbserver.

Great. This is what I was after. I only have the x86 Linux option to test.

> First of all, do you have a copyright assignment?  This is too big to
> take without one.  I see something that looks like you in the
> copyright assignment list, but the associated employer disclaimer is
> expired.

That is me. I will contact the FSF and get this updated.

> 
> After that's taken care of, I'd really appreciate it if you could
> break this up into a couple of logical pieces.  It makes them a lot
> easier to look at.  For instance, the register shadow cache is
> independent of everything else.
> 

Sure that is no problem.

> The pipe changes are user-visible, so we should update the manual.  I
> can take care of that later.

I did notice the documentation and I am fine with getting that in-order.

> 
>> The various low level back-ends have not be changed to printf_filtered or 
>> warning. Should they ?
> 
> Yes, if we document that pipe is available for them.
> 

Ok.

Using the pipe mode to run the linux gdbserver resulted in gdb being 
suspended. I suspect a signal was passed up. It did not show up with the BDM 
back-end because the target is not Unix process. Any ideas where I look ?

Regards
Chris


  reply	other threads:[~2007-11-06  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06  2:15 Chris Johns
2007-11-06  3:34 ` Daniel Jacobowitz
2007-11-06  6:02   ` Chris Johns [this message]
2007-11-06 12:51     ` Daniel Jacobowitz
2007-11-07  4:59       ` Chris Johns

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=47300364.3040000@rtems.org \
    --to=chrisj@rtems.org \
    --cc=gdb-patches@sourceware.org \
    /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