Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: jo@atsresults.com
To: gdb@sources.redhat.com
Subject: Can't debug Threaded application
Date: Wed, 24 Aug 2005 20:18:00 -0000	[thread overview]
Message-ID: <1124914686.430cd5fe3f10a@webmail.atsresults.com> (raw)

Hello Everyone,

I believe the problem I am having is the same a bug 848 and 1154.


GDB 6.3 can't debug a threaded application.  All I get is SIG32s instead of the
[NEW THREAD...] message.  

And when I do a "(gdb)> i thread" I get nothing....

Here are my specs:
- Trustix
- Linux cobra.q1labs.inc 2.4.30-3trsmp #1 Tue Jun 7 22:56:09 ADT 2005 i686
unknown unknown GNU/Linux
- /lib/libc-2.3.2.so
GNU C Library stable release version 2.3.2, by Roland McGrath et al.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.3.
Compiled on a Linux 2.4.25-2tr system on 2004-09-29.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        linuxthreads-0.10 by Xavier Leroy
        BIND-8.2.3-T5B
        libthread_db work sponsored by Alpha Processor Inc
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Report bugs using the `glibcbug' script to <bugs@gnu.org>.

Is there any work arounds for this bug?  I have tried this: 

(gdb)> set auto-solib-add 0 
(gdb)> handle S1G32 nostop noprint

but this only stops the SIG32 from stopping gdb, I still can't properly debug
the program.

What do I have to do to get this to work?

Thanks

Jason






             reply	other threads:[~2005-08-24 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 20:18 jo [this message]
2005-08-29 16:09 ` jo
2005-08-29 16:11   ` Daniel Jacobowitz
2005-08-29 17:06     ` Russell Shaw
2005-08-29 17:08       ` Daniel Jacobowitz
2005-08-29 17:19         ` Russell Shaw

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=1124914686.430cd5fe3f10a@webmail.atsresults.com \
    --to=jo@atsresults.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