From: "H . J . Lu" <hjl@lucon.org>
To: GDB <gdb@sourceware.cygnus.com>
Subject: Re: Is the current gdb 5.1 broken for Linuxthreads?
Date: Mon, 17 Sep 2001 19:13:00 -0000 [thread overview]
Message-ID: <20010917191357.A28300@lucon.org> (raw)
In-Reply-To: <20010917161350.A25349@lucon.org>
On Mon, Sep 17, 2001 at 04:13:50PM -0700, H . J . Lu wrote:
> On Mon, Sep 17, 2001 at 12:47:10PM -0700, H . J . Lu wrote:
> > Here is a modified example from glibc.
> >
> > # gcc -g ex11.c -lpthread -lrt -D_GNU_SOURCE
> > # ./a.out&
> > # ps -xal | grep a.out
> > 000 1103 27904 3705 9 0 247300 600 rt_sig S pts/17 0:00 ./a.out
> > 040 1103 27905 27904 11 0 247300 600 do_pol S pts/17 0:00 ./a.out
> > 040 1103 27906 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27907 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27908 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27909 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27910 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27911 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27912 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27913 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27914 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27915 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27916 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27917 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27918 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27919 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27920 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27921 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27922 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27923 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27924 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27925 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27926 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27927 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27928 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27929 27905 9 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27930 27905 10 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27931 27905 10 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27932 27905 10 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27933 27905 11 0 247300 600 nanosl S pts/17 0:00 ./a.out
> > 040 1103 27934 27905 10 0 247300 600 nanosl S pts/17 0:00 ./a.out
> >
> > # gdb a.out
> > ...
> > (gdb) att 27934
> > Attaching to program: /home/hjl/bugs/gdb/thread/./a.out, process 27934
> > Child process unexpectedly missing: No child processes.
> >
> > Program terminated with signal ?, Unknown signal.
> > The program no longer exists.
> > (gdb)
> >
> > But
> >
> > (gdb) att 27904
> >
> > worked fine. It is a serious regression from gdb 4.18 from RedHat
> > 6.2.
> >
>
> The more I looked at it, the more borken gdb is with linuxthreads:
>
> # gcc -g ex11.c -lpthread -lrt -D_GNU_SOURCE -static
> # a.out
> # gdb a.out
> ...
> (gdb) att 14226
> Attaching to program: /home/hjl/bugs/gdb/thread/a.out, process 14226
> ...
> lin-lwp.c:620: gdb-internal-error: stop_wait_callback: Assertion `pid ==
> GET_LWP (lp->ptid)' failed.
> An internal GDB error was detected. This may make further
It looks like with gdb 5.1, I have to attach the very first thread. Is
that documented anywhere? Shouldn't gdb find the very first thread
and attach it for me?
H.J.
next prev parent reply other threads:[~2001-09-17 19:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 12:47 H . J . Lu
[not found] ` <20010917161350.A25349@lucon.org>
2001-09-17 19:13 ` H . J . Lu [this message]
2001-09-18 13:56 ` H . J . Lu
2001-09-18 15:22 ` RFC: Fix gdb 5.1 for Linuxthreads H . J . Lu
2001-09-19 5:42 ` Duncan Palmer
2001-09-19 9:19 ` H . J . Lu
2001-09-20 8:21 ` Duncan Palmer
2001-09-19 7:06 ` Mark Kettenis
2001-09-19 8:58 ` H . J . Lu
2001-09-19 0:46 ` Is the current gdb 5.1 broken for Linuxthreads? Eli Zaretskii
2001-09-19 8:43 ` H . J . Lu
2001-09-19 6:56 ` Mark Kettenis
2001-09-19 7:39 ` Eric Paire
2001-09-19 9:05 ` H . J . Lu
2001-09-20 0:59 ` Eric Paire
2001-09-19 13:39 ` Andrew Cagney
2001-09-20 1:36 ` Eric Paire
2001-09-20 8:03 ` H . J . Lu
2001-09-20 21:49 ` Eric Paire
2001-09-19 9:10 ` H . J . Lu
2001-09-19 6:32 ` Mark Kettenis
2001-09-19 9:16 ` H . J . Lu
2001-09-21 2:27 James Cownie
2001-09-21 5:04 ` Eric Paire
2001-09-21 5:25 ` James Cownie
2001-09-21 8:35 ` H . J . Lu
2001-09-21 8:39 ` Andrew Cagney
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=20010917191357.A28300@lucon.org \
--to=hjl@lucon.org \
--cc=gdb@sourceware.cygnus.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