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

On Wed, Aug 15, 2007 at 12:36:49PM -0700, Joel Brobecker wrote:
> 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 answer is that you need a bunch of kernel patches for this to
work.  You may want to try a very current kernel; I don't know when
the patches were applied, but I believe they have been at this point.
It was probably some point between 2.6.17 and 2.6.22.

-- 
Daniel Jacobowitz
CodeSourcery


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

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

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=20070815194339.GA2269@caradoc.them.org \
    --to=drow@false.org \
    --cc=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