This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
gdb suspends itself
- From: Klaus Zeitler <kzeitler at lucent dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 05 Jul 2005 10:44:25 +0200
- Subject: gdb suspends itself
Hello,
I'm trying to debug a program with approx. 100 threads under Solaris 5.8,
that generates lots of trace data. When I run the program under gdb,
the first few threads are started, then gdb suspends itself and I need to
call 'fg' to resume execution, i.e. the whole thing looks like e.g.:
[674]$ gdb ./umc.vx
GNU gdb 6.3.0.20050704-cvs
...
[New LWP 27]
UMC1-1-> [07-05 10:05:41:932930] (tMain ) : Smdev: SMDEV initialization succeeded!
[New LWP 28]
logMsg [07-05 10:05:42:849879] (FireWire ) : PetDemon create Server socket on port 45263
UMC1-1-> [07-05 10:05:42:870024] 0x13dd7d0 (tFtpdTask ) : waiting for a new client connection...
UMC1-1-> [07-05 10:05:42:981463] 0x7277b0 (tMain ) : Initializing OSipc
[6]+ Stopped gdb ./umc.vx
[675]$ fg
gdb ./umc.vx
---Type <return> to continue, or q <return> to quit---
[New LWP 29]
logMsg [07-05 10:20:36:924936] (nbapDemon ) : PetDemon create Server socket on port 45260
...
The same happens with gdb 5.3. and 6.1.
This is probably not a gdb problem, but I hope someone can give me a hint
how I should investigate this odd behavior.
Thanks
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
There are very few personal problems that cannot be solved
through a suitable application of high explosives.