public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jaydesh9 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15828] New: GDB crashed during process attachment when that process was dumping its own core due to a fault
Date: Fri, 09 Aug 2013 22:56:00 -0000 [thread overview]
Message-ID: <bug-15828-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15828
Bug ID: 15828
Summary: GDB crashed during process attachment when that
process was dumping its own core due to a fault
Product: gdb
Version: 7.4
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: jaydesh9 at gmail dot com
While attaching GDB to already running process with -p option, gdb crashed as ,
corresponding process was in the middle of its own crash .
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found).
..done.
warning: td_ta_new failed: generic error
warning: td_ta_new failed: generic error
warning: Unable to find libthread_db matching inferior's thread library, th
read debugging will not be available.
Loaded symbols for /lib64/libpthread.so.0
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done
.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols fo
und)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /usr/lib64/libcxgb3-rdmav2.so...done.
Loaded symbols for /usr/lib64/libcxgb3-rdmav2.so
Reading symbols from /usr/lib64/libmthca-rdmav2.so...done.
Loaded symbols for /usr/lib64/libmthca-rdmav2.so
Reading symbols from /usr/lib64/libnes-rdmav2.so...done.
Loaded symbols for /usr/lib64/libnes-rdmav2.so
Reading symbols from /usr/lib64/libmlx4-rdmav2.so...done.
Loaded symbols for /usr/lib64/libmlx4-rdmav2.so
Reading symbols from /usr/lib64/libmlx4-m-rdmav2.so...done.
Loaded symbols for /usr/lib64/libmlx4-m-rdmav2.so
Cannot access memory at address 0x7f0bff1eb188
warning: td_ta_new failed: generic error
warning: td_ta_new failed: generic error
warning: Unable to find libthread_db matching inferior's thread library, th
read debugging will not be available.
Failed to read a valid object file image from memory.
0x00007f0bf4e85f95 in pthread_join () from /lib64/libpthread.so.0
(gdb) c
Continuing.
0x00007f0bf4e85f95 in pthread_join () from /lib64/libpthread.so.0
ptrace: No such process.
(gdb) c
Continuing.
0x00007f0bf4e85f95 in pthread_join () from /lib64/libpthread.so.0
ptrace: No such process.
(gdb) c
Continuing.
0x00007f0bf4e85f95 in pthread_join () from /lib64/libpthread.so.0
ptrace: No such process.
(gdb) q
A debugging session is active.
Inferior 1 [process 11892] will be detached.
Quit anyway? (y or n) n
Not confirmed.
(gdb) q
A debugging session is active.
Inferior 1 [process 11892] will be detached.
Quit anyway? (y or n) y
[process 11892 exited]
linux-nat.c:1766: internal-error: linux_nat_detach: Assertion `num_lwps (GE
T_PID (inferior_ptid)) == 1' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
linux-nat.c:1766: internal-error: linux_nat_detach: Assertion `num_lwps (GE
T_PID (inferior_ptid)) == 1' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-08-09 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 22:56 jaydesh9 at gmail dot com [this message]
2013-08-09 23:13 ` [Bug gdb/15828] " jaydesh9 at gmail dot com
2024-01-01 16:43 ` ssbssa at sourceware dot org
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-15828-4717@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).