From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Make monitor targets always have a thread
Date: Mon, 07 Jul 2008 19:12:00 -0000 [thread overview]
Message-ID: <20080707191235.GD11544@caradoc.them.org> (raw)
In-Reply-To: <200807031623.29562.pedro@codesourcery.com>
On Thu, Jul 03, 2008 at 04:23:29PM +0100, Pedro Alves wrote:
> Does it look OK? Can anyone instruct me how to test this; or do a test
> spin for me; or claim that it looks ok, and we'll fix problems as
> they arise? :-)
It's OK. I don't have any way to test monitor either.
> +/* This is the ptid we use while we're connected to a monitor. It's
Its
> + value is arbitrary, as monitor targets don't have a notion or
notion of
> + processes or thread, but we need something non-null to place in
threads
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-07 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 15:23 Pedro Alves
2008-07-03 18:04 ` Make remote-sim target " Pedro Alves
2008-07-04 15:00 ` fix load command bug [was : Re: Make remote-sim target always have a thread] Pedro Alves
2008-07-07 19:20 ` Daniel Jacobowitz
2008-07-09 11:18 ` Pedro Alves
2008-07-07 19:15 ` Make remote-sim target always have a thread Daniel Jacobowitz
2008-07-09 10:53 ` [ob] don't skip most of the testsuite... [was: Re: Make remote-sim target always have a thread] Pedro Alves
2008-07-09 12:36 ` Daniel Jacobowitz
2008-07-09 11:11 ` Make remote-sim target always have a thread Pedro Alves
2008-07-09 12:39 ` Daniel Jacobowitz
2008-07-07 19:12 ` Daniel Jacobowitz [this message]
2008-07-07 19:16 ` Make monitor targets " Stan Shebs
2008-07-07 19:22 ` Daniel Jacobowitz
2008-07-07 19:51 ` Stan Shebs
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=20080707191235.GD11544@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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