From: "Oleg V. Zhylin" <ovz@yahoo.com>
To: gdb@sourceware.org
Subject: gdb Stopped in pthread_create
Date: Mon, 23 Jul 2007 09:52:00 -0000 [thread overview]
Message-ID: <330935.17438.qm@web56610.mail.re3.yahoo.com> (raw)
Hi All,
I've tried to debug my multithreaded application with gdb 6.6 (GNU
gdb Red Hat Linux (6.6-15.fc7rh) ), but inside pthread_create call I
get
[1]+ Stopped gdb ./a.out
If I use ddd on the same machine pthread_create works just fine.
I get this error on all Linux boxes and GUI is not available on all of
them. Is there a way to configure gdb so that it could tolerate
pthread_create?
WBR Oleg V. Zhylin ovz@yahoo.com
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting
next reply other threads:[~2007-07-21 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 9:52 Oleg V. Zhylin [this message]
2007-07-23 19:22 ` Jim Blandy
2007-07-24 9:11 ` breaking at thread exit Mayuresh Kulkarni
2007-07-24 15:50 ` gdb Stopped in pthread_create Oleg V. Zhylin
2007-07-28 1:40 ` Jim Blandy
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=330935.17438.qm@web56610.mail.re3.yahoo.com \
--to=ovz@yahoo.com \
--cc=gdb@sourceware.org \
/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