public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>,
	Joel Brobecker <brobecker@adacore.com>,
	<gdb-patches@sourceware.org>
Cc: <sergiodj@redhat.com>, <tom@tromey.com>, <Ulrich.Weigand@de.ibm.com>
Subject: Re: GDB 8.1 branching 2017-12-11 update
Date: Mon, 11 Dec 2017 16:57:00 -0000	[thread overview]
Message-ID: <4b9d41af-3a07-1e75-6118-595bb73f7ec4@ericsson.com> (raw)
In-Reply-To: <bb3e633b-defa-02c6-93de-cb33a07fb031@redhat.com>

On 2017-12-11 09:33 AM, Pedro Alves wrote:
> On 12/11/2017 01:56 PM, Joel Brobecker wrote:
> 
>> Aside from that, we have a number of entries which have been identified
>> as blocking for 8.1 (so branching would be OK, but we would wand to
>> fix them before we make the official release):
>>
>>   * [Pedro] gdb/22556
>>     Regression: gdb.threads/names.exp with --target_board=native-gdbserver
> 
> Note: if someone could help with this one, I'd appreciate it.
> Just doing a git bisect to find what caused this would help.

Well, it's a test I added, and the offending commit is mine:

  remote: C++ify thread_item and threads_listing_context
  21fe1c752e254167d953fa8c846280f63a3a5290

So I guess I don't really have a choice but to look at this.

Simon

  reply	other threads:[~2017-12-11 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 13:56 Joel Brobecker
2017-12-11 14:31 ` Ulrich Weigand
2017-12-11 14:33 ` Pedro Alves
2017-12-11 16:57   ` Simon Marchi [this message]
2017-12-11 18:22     ` Simon Marchi
2017-12-11 15:10 ` Simon Marchi
2017-12-15 20:37 ` Sergio Durigan Junior

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=4b9d41af-3a07-1e75-6118-595bb73f7ec4@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@redhat.com \
    --cc=tom@tromey.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).