This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Non-intrusive remote GDB
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Shrikanth Kamath <shrikanth07 at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Sun, 15 May 2011 14:52:17 +0200
- Subject: Re: Non-intrusive remote GDB
- References: <BANLkTim7sP_W1ae+4byRiJMeJgjau+A2cw@mail.gmail.com>
On Wed, 11 May 2011 19:40:39 +0200, Shrikanth Kamath wrote:
> My question is it possible / feasible to attempt the remote GDB attach
> only to single micro kernel thread in the PPC plane
> and not halt it totally? Say the other threads proceed as normal.
During the initial attach normally all the threads get attached and they get
stopped by the attachment. Later you can have stopped only one specific
thread by using non-stop mode:
$ info '(gdb)Non-Stop Mode'
To not to stop the other threads at all one needs to disallow finding
gdbserver the file libthread_db.so.1, besides reconfiguring GDB as a safe bet
you can rename/hide it on the PPC board. `info threads' shows only the
single/initial thread.
(Assuming GNU/Linux environment on the PPC borad; you did not say.)
Regards,
Jan