From: Simon Marchi <simon.marchi@ericsson.com>
To: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Cc: <keiths@redhat.com>, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: GDB 7.10 release 2015-07-17 status update?
Date: Fri, 17 Jul 2015 20:15:00 -0000 [thread overview]
Message-ID: <55A96255.9000301@ericsson.com> (raw)
In-Reply-To: <20150717175328.GA15874@adacore.com>
On 15-07-17 01:53 PM, Joel Brobecker wrote:
> I've moved the following item to the Exclude list, as per Pedro's
> recommendation:
>
> - PR gdb/18600 (After forking and threads spawning, gdb leaves newly
> created threads stopped) (too delicate)
Have I missed something? Pedro said that about changing the behavior of
when the prompt returns when an inferior exits (see [1]). I don't recall
him saying that about the fix for 18600 though. I was actually planning
early next week to formalize and submit the patches he sent in that thread,
hoping they could find their way into 7.10.
[1] https://sourceware.org/ml/gdb-patches/2015-07/msg00384.html
next prev parent reply other threads:[~2015-07-17 20:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 17:53 Joel Brobecker
2015-07-17 18:14 ` Luis Machado
2015-07-17 18:32 ` Joel Brobecker
2015-07-17 18:38 ` Luis Machado
2015-07-17 19:06 ` Eli Zaretskii
2015-07-17 20:48 ` Joel Brobecker
2015-07-17 20:57 ` Luis Machado
2015-07-20 10:13 ` Iain Buclaw
2015-07-21 17:16 ` Joel Brobecker
2015-07-17 19:04 ` Eli Zaretskii
2015-07-17 19:03 ` Eli Zaretskii
2015-07-24 9:26 ` Pedro Alves
2015-07-24 14:31 ` Iain Buclaw
2015-07-24 14:37 ` Pedro Alves
2015-07-17 18:25 ` Keith Seitz
2015-07-17 18:28 ` Jan Kratochvil
2015-07-17 18:35 ` Joel Brobecker
2015-07-17 20:15 ` Simon Marchi [this message]
2015-07-17 20:57 ` Joel Brobecker
2015-07-17 21:00 ` Simon Marchi
2015-07-17 20:24 ` Sergio Durigan Junior
2015-07-20 10:06 ` Yao Qi
2015-07-21 17:11 ` Joel Brobecker
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=55A96255.9000301@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).