This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
'target remote' and the return of pid 42000
- From: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- To: <gdb at sourceware dot org>
- Date: Fri, 8 May 2009 12:04:49 -0400
- Subject: 'target remote' and the return of pid 42000
Hi,
I'm trying out the different debugging configurations with HEAD (from a
week ago).
Currently, I'm trying remote debugging with gdbserver.
I'm starting a gdbserver on a remote Linux with:
> gdbserver.7.0 :10008 ~/a.out
When I use 'target remote' to connect to it, the pid reported by
GDB is 42000.
I know this pid is used when the real pid is not known. However,
when using 'target extended-remote' GDB reports the proper pid.
Is this normal behavior?
(note that I see the pid 42000 using both -list-thread-groups
and info inferior.)
Thanks
marc