* 'target remote' and the return of pid 42000
@ 2009-05-08 16:05 Marc Khouzam
2009-05-08 16:09 ` Pedro Alves
0 siblings, 1 reply; 2+ messages in thread
From: Marc Khouzam @ 2009-05-08 16:05 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 'target remote' and the return of pid 42000
2009-05-08 16:05 'target remote' and the return of pid 42000 Marc Khouzam
@ 2009-05-08 16:09 ` Pedro Alves
0 siblings, 0 replies; 2+ messages in thread
From: Pedro Alves @ 2009-05-08 16:09 UTC (permalink / raw)
To: gdb; +Cc: Marc Khouzam
On Friday 08 May 2009 17:04:49, Marc Khouzam wrote:
> 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?
Yes, "target remote" doesn't support the remote multi-process
extensions; only "target extended-remote" does.
--
Pedro Alves
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-05-08 16:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-05-08 16:05 'target remote' and the return of pid 42000 Marc Khouzam
2009-05-08 16:09 ` Pedro Alves
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox