From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: Don't try to report resumed thread it the thread list is empty.
Date: Wed, 09 Jul 2008 13:04:00 -0000 [thread overview]
Message-ID: <200807091403.36260.pedro@codesourcery.com> (raw)
In-Reply-To: <200807091352.28573.pedro@codesourcery.com>
A Wednesday 09 July 2008 13:52:28, Pedro Alves wrote:
> A Wednesday 09 July 2008 13:04:11, Vladimir Prus wrote:
> > I'm not sure which way we want to make it consistent. Outputiing
> > "thread-id" with a "I don't exist" value of thread id seems a little bit
> > distasteful. I guess I can modify regexp to make thread-id optional.
>
> I meant either output -thread-id="0" everywhere, or don't output -thread=id
> at all, nowhere.
To be clear, I don't care that much about this inconsistency, what
I really want to have all targets register at least a thread, so
modifying the regexp is also fine with me, FWIW. Although I thought
that changing the code in this case would be a less invasive change, than
relaxing the testsuite.
--
Pedro Alves
prev parent reply other threads:[~2008-07-09 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 17:58 Vladimir Prus
2008-07-09 10:31 ` Pedro Alves
2008-07-09 12:04 ` Vladimir Prus
2008-07-09 12:52 ` Pedro Alves
2008-07-09 13:04 ` Pedro Alves [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=200807091403.36260.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@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