This is the mail archive of the gdb@sourceware.org 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]
Other format:	[Raw text]

Re: Restarting gdbserver

From: Leon Pollak <leonp at plris dot com>
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
Cc: gdb at sourceware dot org
Date: Thu, 20 Jan 2011 16:11:37 +0200
Subject: Re: Restarting gdbserver
References: <201101201129.50875.leonp@plris.com> <20110120093635.GA5601@host1.dyn.jankratochvil.net>

On Thursday January 20 2011, Jan Kratochvil wrote:
> or also:
> 	gdbserver --multi COMM
> 	using `target extended-remote ...' instead.
WOW!!!!!!!!
How could I not find this!!??
1001 of thanks!
Works fine. I start thegdb with:

set sysroot /opt/FS/
set remote exec-file /common/csu
target extended-remote 192.168.50.4:44000
---
The only one problem left for me is that when stopped/broken, the stack frame 
is not presented as it usually is:

(gdb) frame
#0  0x400314bc in pthread_cond_wait@@GLIBC_2.4 () from 
/opt/FS/lib/libpthread.so.0

And nothing else...:-(

Thousands of thanks ahead for the help...
-- 
Leon

Follow-Ups:
- Re: Restarting gdbserver
  - From: Jan Kratochvil

References:
- Restarting gdbserver
  - From: Leon Pollak
- Re: Restarting gdbserver
  - From: Jan Kratochvil

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]