From: Chris Johns <chrisj@rtems.org>
To: gdb-patches@sourceware.org
Subject: Re: gdbserver pipe, xml and monitor changes
Date: Wed, 07 Nov 2007 04:59:00 -0000 [thread overview]
Message-ID: <47314612.4060401@rtems.org> (raw)
In-Reply-To: <20071106125118.GA22174@caradoc.them.org>
Daniel Jacobowitz wrote:
>
> This probably happens because GDB is careful about job control
> (particularly tcsetpgrp) and gdbserver isn't. Or maybe it's because
> oth are too careful about job control.
>
Ok. I will take a look.
> This may be a rat's nest. If we can't get it to work, perhaps we
> should restrict pipe to non-native targets.
That would be a shame as the pipe option does allow you to have gdb run ssh
and the gdbserver without anything special happening.
Regards
Chris
prev parent reply other threads:[~2007-11-07 4:59 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
2007-11-06 12:51 ` Daniel Jacobowitz
2007-11-07 4:59 ` Chris Johns [this message]
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=47314612.4060401@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