From: Simon Marchi <simark@simark.ca>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix re-runs of a second inferior (PR gdb/25410)
Date: Fri, 24 Jan 2020 15:02:00 -0000 [thread overview]
Message-ID: <28a65882-8c59-db61-418c-1dc2139481af@simark.ca> (raw)
In-Reply-To: <DM6PR11MB303390E9124B6ECD67E1740AC40E0@DM6PR11MB3033.namprd11.prod.outlook.com>
On 2020-01-24 6:22 a.m., Aktemur, Tankut Baris wrote:
> On Friday, January 24, 2020 4:02 AM, Pedro Alves wrote:
>> This fixes a latent bug exposed by the multi-target patch (5b6d1e4fa
>> "Multi-target support).
>
> The patch led to the assertion violation below when running
> gdb.threads/vfork-follow-child-exit.exp.
>
> gdb/progspace.c:243: internal-error: void set_current_program_space(program_space*): Assertion `pspace != NULL' failed.
Oh, I see that too.
Simon
next prev parent reply other threads:[~2020-01-24 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 3:32 Pedro Alves
2020-01-24 7:00 ` Simon Marchi
[not found] ` <DM6PR11MB303390E9124B6ECD67E1740AC40E0@DM6PR11MB3033.namprd11.prod.outlook.com>
2020-01-24 15:02 ` Simon Marchi [this message]
2020-01-24 15:23 ` Pedro Alves
2020-01-24 17:15 ` Simon Marchi
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=28a65882-8c59-db61-418c-1dc2139481af@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tankut.baris.aktemur@intel.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