This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug tdep/15420] New: Thread support broken on 64-bit Solaris/x86
- From: "ro at TechFak dot Uni-Bielefeld.DE" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 30 Apr 2013 14:56:57 +0000
- Subject: [Bug tdep/15420] New: Thread support broken on 64-bit Solaris/x86
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15420
Bug #: 15420
Summary: Thread support broken on 64-bit Solaris/x86
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
AssignedTo: unassigned@sourceware.org
ReportedBy: ro@TechFak.Uni-Bielefeld.DE
CC: brobecker@adacore.com
Classification: Unclassified
Host: amd64-pc-solaris2.1[01]
Target: amd64-pc-solaris2.1[01]
Build: amd64-pc-solaris2.1[01]
This report is about gdb 7.6, but bugzilla doesn't yet provide that version.
When I start gdb, configured on Solaris 10/x86 with
configure CFLAGS='-g -O2 -m64' --prefix=/vol/gcc --disable-nls --without-python
I get this warning:
[GDB will not be able to debug user-mode threads: ld.so.1: gdb-7.6: fatal:
relocation error: file /lib/64/libthread_db.so.1: symbol ps_lgetxregsize:
referenced symbol not found]
This is a regression from gdb 7.5 where this worked and the function (required
by libthread_db.so.1) was provided by the gdb binary. This is obviously due to
this change:
2012-09-27 Joel Brobecker <brobecker@adacore.com>
* sol-thread.c (ps_lgetxregsize, ps_lgetxregs, ps_lsetxregs):
Move these functions to sparc-sol-thread.c.
* sparc-sol-thread.c: New file.
* configure.ac: Add sparc-sol-thread.o to CONFIG_OBS and
sparc-sol-thread.c to CONFIG_SRCS for sparc-solaris native
configurations.
* configure: Regenerate.
The functions are incorrectly taken to be sparc-specific. If I add
sparc-sol-thread.c to the Solaris/x86 build by editing configure, gdb starts
again as expected.
Rainer
--
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.