From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] infrun: don't resume the inferior when we notice a new thread (new_thread_event).
Date: Wed, 06 Jun 2012 18:12:00 -0000 [thread overview]
Message-ID: <4FCF9D8F.6010807@redhat.com> (raw)
In-Reply-To: <20120528204623.25996.69879.stgit@brno.lan>
On 05/28/2012 09:46 PM, Pedro Alves wrote:
> gdb/
> 2012-05-28 Pedro Alves <palves@redhat.com>
>
> * infrun.c (struct execution_control_state): Remove
> `new_thread_event' field.
> (handle_inferior_event): Simplify new threads handling; don't
> resume the inferior if we find a new thread.
>
> gdb/testsuite/
> 2012-05-28 Pedro Alves <palves@redhat.com>
>
> * gdb.threads/clone-new-thread-event.c: New file.
> * gdb.threads/clone-new-thread-event.exp: New file.
I've applied this now.
--
Pedro Alves
prev parent reply other threads:[~2012-06-06 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 20:46 Pedro Alves
2012-05-28 21:19 ` Jan Kratochvil
2012-05-28 21:27 ` Pedro Alves
2012-06-06 18:12 ` 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=4FCF9D8F.6010807@redhat.com \
--to=palves@redhat.com \
--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