linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maarten de Boer <mdeboer@iua.upf.es>
To: bug-glibc@gnu.org, <linux-kernel@vger.kernel.org>,
	<gdb@sources.redhat.com>
Subject: Re: gdb problem with kernel 2.6.0 and pthreads
Date: Thu, 8 Jan 2004 16:44:47 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.44.0401081643400.1419-100000@iua-mail.upf.es> (raw)
In-Reply-To: <20040107174932.7d7b9542.mdeboer@iua.upf.es>


As suggested by several people, moving to gdb 6.0 solves the problem,
so for the record.

Thanks,

Maarten

> Hello,
>
> Sorry for cross-posting, but I have a problem that I am not sure whom
> to address... Google did not reveal anything helpfull.
>
> I resently moved to kernel 2.6.0 (on Debian Sarge), and while everything
> seems to work just fine, to my surprise gdb now fails to debug
> executables that are linked against pthread:
>
> GNU gdb 5.3-debian
> [snip]
> This GDB was configured as "i386-linux"...
> (gdb) b main
> Breakpoint 1 at 0x80483a4: file foo.c, line 3.
> (gdb) r
> Starting program: /root/a.out
> Error while reading shared library symbols:
> Cannot find new threads: capability not available
> Cannot find user-level thread for LWP 714: capability not available
>
> With kernel 2.4.22 this problem did not occur. Do you have any idea what
> may have caused this problem, and how to solve it? If I can provide you
> with any information that could be helpfull, please let me know.
>
> Kind regards,
>
> Maarten
>
> gcc version 3.3.2 (Debian)
> GNU gdb 5.3-debian
> GNU libc 2.3.2
>
>
>


      reply	other threads:[~2004-01-08 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 16:49 gdb problem with kernel 2.6.0 and pthreads Maarten de Boer
2004-01-08 16:44 ` Maarten de Boer [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=Pine.LNX.4.44.0401081643400.1419-100000@iua-mail.upf.es \
    --to=mdeboer@iua.upf.es \
    --cc=bug-glibc@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).