This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH] Fix re-runs of a second inferior (PR gdb/25410)


On Friday, January 24, 2020 6:05 PM, Simon Marchi wrote:
> On 2020-01-24 10:11 a.m., Pedro Alves wrote:
> > On 1/24/20 2:59 PM, Simon Marchi wrote:
> >> 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.
> >
> > Me too.  No idea how I missed this.  Sorry about that...
> > There's actually yet another internal error in addition
> > to that one.
> >
> > Here's the updated patch, which fixes all.
> >

<snipped>

> > The fix is to use scoped_restore_current_pspace_and_thread instead of
> > scoped_restore_current_thread.
> 
> I did not look at the code in depth, but your explanations make sense to me,
> so if the testsuite shows no regression, this LGTM.
> 
> Simon

I ran the patch locally and did not see any regression.
Thank you.

-Baris

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]