public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/13719] gdb: Cannot find new threads: generic error [testcase]
Date: Mon, 02 Apr 2012 14:43:00 -0000 [thread overview]
Message-ID: <bug-13719-4717-pefL63jYbe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13719-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13719
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-04-02 14:42:43 UTC ---
FWIW, I could not reproduce this on Fedora 16:
(gdb) run
Starting program: /home/tromey/gnu/PRS/gdb13719/pr
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Inferior 1 (process 21325) exited normally]
[Inferior 21325 exited]
I even disabled debuginfo lookup:
(gdb) set debug-file-directory /
... and it still worked.
I have:
barimba. rpm -q glibc
glibc-2.14.90-24.fc16.6.x86_64
I tried CVS HEAD (from last week or so), 7.3, 7.4, and the system gdb.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-04-02 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 9:05 [Bug threads/13719] New: " jengelh at medozas dot de
2012-04-02 12:01 ` [Bug threads/13719] " rguenth at gcc dot gnu.org
2012-04-02 14:43 ` tromey at redhat dot com [this message]
2012-04-02 14:49 ` rguenth at gcc dot gnu.org
2012-07-22 20:08 ` jengelh at inai dot de
2012-07-23 7:55 ` rguenther at suse dot de
2012-07-23 8:32 ` jan.kratochvil at redhat dot com
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=bug-13719-4717-pefL63jYbe@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).