'target remote' and the return of pid 42000

[Pedro Alves]

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