public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: kevinb@redhat.com, scox@redhat.com, palves@redhat.com,
	gdb-patches@sourceware.org
Subject: Re: GDB 8.2 release 2018-08-21 status update
Date: Tue, 21 Aug 2018 20:54:00 -0000	[thread overview]
Message-ID: <20180821205443.GD24065@adacore.com> (raw)
In-Reply-To: <cb286a3a84f719a1aea1df3ad1833076@polymtl.ca>

> The failure seems to have been introduced by c12a508 ("Add
> client_state struct.") as well.

Thanks Simon. That made me want to check this commit for the PR I said
I would check...

  * [*UNASSIGNED* (Joel???)] PR gdb/23374
    gdb.base/execl-update-breakpoints.exp, with --target_board=native-gdbserver
    https://sourceware.org/bugzilla/show_bug.cgi?id=23374

        No problem with native debugging, or when using the native
        gdbserver in extended-remote mode.

... and indeed, it's also caused, somehow, by commit c12a508.

-- 
Joel

  reply	other threads:[~2018-08-21 20:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 17:51 Joel Brobecker
2018-08-21 18:33 ` Kevin Buettner
2018-08-21 19:02 ` Simon Marchi
2018-08-21 20:17   ` Simon Marchi
2018-08-21 20:54     ` Joel Brobecker [this message]
2018-08-22 16:07       ` Simon Marchi
2018-08-22 17:38         ` Simon Marchi
2018-08-22 18:03         ` Stan Cox
2018-08-22 18:09           ` Simon Marchi
2018-08-21 20:55 ` Joel Brobecker
2018-08-21 21:29   ` Simon Marchi
2018-08-23 17:56     ` Pedro Alves
2018-08-24 18:01       ` Pedro Alves
2018-08-23 18:37 ` Simon Marchi
2018-08-23 22:41   ` Kevin Buettner
2018-08-24 18:35     ` Pedro Alves
2018-08-24 19:15       ` Simon Marchi
2018-08-24 19:52         ` Pedro Alves
2018-08-24  3:57 ` Kevin Buettner
2018-08-25  5:41   ` Kevin Buettner

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=20180821205443.GD24065@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=palves@redhat.com \
    --cc=scox@redhat.com \
    --cc=simon.marchi@polymtl.ca \
    /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).