This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug tdep/16940] New: S390: 64-bit GDB can't debug multithreaded 31-bit inferior
- From: "arnez at linux dot vnet.ibm.com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 13 May 2014 13:59:56 +0000
- Subject: [Bug tdep/16940] New: S390: 64-bit GDB can't debug multithreaded 31-bit inferior
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16940
Bug ID: 16940
Summary: S390: 64-bit GDB can't debug multithreaded 31-bit
inferior
Product: gdb
Version: 7.7
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: arnez at linux dot vnet.ibm.com
When debugging a multithreaded 31-bit inferior (compiled with "gcc -m31
-lpthread), a 64-bit gdb usually crashes like this:
(gdb) run
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7d68cb80 (LWP 21445)]
warning: Can't attach LWP -844998064: No child processes
linux-thread-db.c:434: internal-error: thread_get_info_callback: Assertion
`inout->thread_info != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
This is caused by a bad offset in fill_gregset() since commit
2ccd146855365598ad2644ef8139f2f2a6747b90
(https://sourceware.org/ml/gdb-patches/2013-09/msg00355.html).
The same bug also causes failures with inferior function calls.
--
You are receiving this mail because:
You are on the CC list for the bug.