This is the mail archive of the gdb@sourceware.cygnus.com 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]

Re: [PATCH] remote_detach() and inferior_pid

To: Jim Kingdon <kingdon at redhat dot com>
Subject: Re: [PATCH] remote_detach() and inferior_pid
From: Andrew Cagney <ac131313 at cygnus dot com>
Date: Thu, 17 Feb 2000 19:14:36 +1100
CC: gdb at sourceware dot cygnus dot com
Organization: Cygnus Solutions
References: <14505.29243.656290.516276@kwikemart.cygnus.com> <bd7pynspv.fsf@rtl.cygnus.com>

Jim Kingdon wrote:
> 
> > This happens because remote_detach() (and remote_async_detach()) do
> > not reset inferior_pid to 0. Is there a reason for this being this
> > way?
> 
> Setting inferior_pid to 0 sounds good.  I'm not completely sure why
> the *_detach functions don't just call generic_mourn_inferior.

Would that kill the target?  Dig dig dig.  Nope!

Yes, generic_mourn_inferior looks to be doing the correct thing - namely
pulling breakpoints and the like.

	Andrew

References:
- [PATCH] remote_detach() and inferior_pid
  - From: Elena Zannoni
- Re: [PATCH] remote_detach() and inferior_pid
  - From: Jim Kingdon

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