Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: debugging threads on 64bit GNU/Linux with 32bit debugger?
Date: Wed, 15 Aug 2007 19:33:00 -0000	[thread overview]
Message-ID: <20070815193649.GH24369@adacore.com> (raw)

Hello,

I have a feeling this is a familiar question, but I'm still unsure at
the answer after my searches on this list as well as on the general web.

Here is the situation: We're using a gcc/gdb toolset built on a 32bit
x86-linux machine. We're using this toolset on a 64bit machine running
a 64bit GNU/Linux machine. The resulting executable is runing in 32bit
compatibility mode.

Everything seems to be working fine, except that we're having trouble
debugging threaded apps. The thread library used is the NPTL, and the
debugger is reporting to use what seems to be the correct (32bit)
instance of the libthread_db library (the 32bit version in /lib/tls,
not the one in /lib64/tls).

The debugger fails at startup time saying:

        [Thread debugging using libthread_db enabled]
        Cannot find new threads: generic error

The version info of the C library our application is using reads:

    % /lib/tls/libc.so.6
    GNU C Library stable release version 2.3.5 (20050720), by Roland McGrath et
+al.
    Copyright (C) 2005 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.
    Configured for i686-suse-linux.
    Compiled by GNU CC version 3.3.3 (SuSE Linux).
    Compiled on a Linux 2.6.5 system on 2006-08-09.
    Available extensions:
            GNU libio by Per Bothner
            crypt add-on version 2.1 by Michael Glad and others
            Native POSIX Threads Library by Ulrich Drepper et al
            GNU Libidn by Simon Josefsson
            NoVersion patch for broken glibc 2.0 binaries
            BIND-8.2.3-T5B
            NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
    Thread-local storage support included.
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/libc/bugs.html>.

Is our setup supposed to work? Is this a known issue of this
version of the libc (I saw that glibc is now at version 2.6)?
Any hint?

Thanks a lot,
-- 
Joel


             reply	other threads:[~2007-08-15 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 19:33 Joel Brobecker [this message]
2007-08-15 19:43 ` Daniel Jacobowitz

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=20070815193649.GH24369@adacore.com \
    --to=brobecker@adacore.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