Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rob Kramer <robk@starhub.net.sg>
To: gdb@sourceware.org
Subject: Missing thread support..
Date: Mon, 14 Aug 2006 15:58:00 -0000	[thread overview]
Message-ID: <200608142352.23711.robk@starhub.net.sg> (raw)

Hi,

When trying to find a deadlock in my program, I noticed my gdb (6.4 for 
i586-linux target, cross-compiled by OpenEmbedded) lacks thread support. It 
doesn't detect when a new thread starts, and 'info threads' always returns an 
empty list. Below is the output on i586-linux, versus a proper setup that 
works as expected:

OpenEmbedded distro (gdb 6.4):
--------------------
This GDB was configured as "i586-linux"...Using host libthread_db library 
"/lib/libthread_db.so.1".

(gdb) r 2
Starting program: /home/root/phello 2
Hello from node 0
Hello from node 1
--------------------


SUSE 10.1 (gdb 6.3):
--------------------
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db 
library "/lib/libthread_db.so.1".

(gdb) r 2
Starting program: /home/rob/phello 2
[Thread debugging using libthread_db enabled]
[New Thread -1210440016 (LWP 13673)]
[New Thread -1210442848 (LWP 13676)]
Hello from node 0
Hello from node 1
--------------------


I've probably misconfigured or mis-crosscompiled my gdb, but how can I find 
out where I should start looking? Is there a way gdb can tell me why it 
doesn't support thread debugging? Do the config.{log|status} files record 
what might be wrong? (It all seems correct to me)

Glibc is version 2.4, (cross) gcc is 4.1.1, linux 2.6.16.27.

Cheers!

     Rob


-- 
1.8026175e+12 furlongs per fortnight.


             reply	other threads:[~2006-08-14 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 15:58 Rob Kramer [this message]
2006-08-14 20:59 ` Daniel Jacobowitz
2006-08-15  2:35   ` Rob Kramer

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=200608142352.23711.robk@starhub.net.sg \
    --to=robk@starhub.net.sg \
    --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