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: Elena Zannoni <ezannoni at cygnus dot com>
Date: Tue, 15 Feb 2000 15:03:53 -0500 (EST)
Cc: gdb at sourceware dot cygnus dot com
Newsgroups: cygnus.gdb
References: <14505.29243.656290.516276@kwikemart.cygnus.com><bd7pynspv.fsf@rtl.cygnus.com>

Jim Kingdon writes:
 > > 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.
 > 
 > 

Yes, I was thinking about that too. Maybe just calling
generic_mourn_inferior is the best way to make sure that all is
cleaned up as it should be.

Elena

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]