From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb@sources.redhat.com
Subject: gdb suspends itself
Date: Tue, 05 Jul 2005 09:13:00 -0000 [thread overview]
Message-ID: <q5gy88l4p7a.fsf@lucent.com> (raw)
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.
next reply other threads:[~2005-07-05 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 9:13 Klaus Zeitler [this message]
2005-07-05 11:05 ` Vladimir Prus
2005-07-06 9:27 ` Klaus Zeitler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q5gy88l4p7a.fsf@lucent.com \
--to=kzeitler@lucent.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox