This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: server/2286: gdbserver opens socket and waits for connectioneven if child fork fails
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 17 Jul 2007 22:28:01 -0000
- Subject: Re: server/2286: gdbserver opens socket and waits for connectioneven if child fork fails
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR server/2286; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: michael.snyder@access-company.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: server/2286: gdbserver opens socket and waits for connection
even if child fork fails
Date: Tue, 17 Jul 2007 18:25:40 -0400
On Tue, Jul 17, 2007 at 08:28:21PM -0000, Michael Snyder wrote:
> Tell gdbserver to launch a program that doesn't exist
> (eg. if you typed the name wrong). It will try to fork
> the process, and fail of course, but despite the failure
> it will still open a socket and wait for gdb to connect.
>
> As soon as gdb connects, gdbserver will close and exit.
Could you check if this still happens in HEAD? I know I did
_something_ related to this, but I don't remember if it was the same
bug exactly.
--
Daniel Jacobowitz
CodeSourcery