public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at TechFak dot Uni-Bielefeld.DE" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/15420] New: Thread support broken on 64-bit Solaris/x86
Date: Tue, 30 Apr 2013 14:56:00 -0000 [thread overview]
Message-ID: <bug-15420-4717@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2013-04-30 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 14:56 ro at TechFak dot Uni-Bielefeld.DE [this message]
2013-05-01 6:43 ` [Bug tdep/15420] " brobecker at gnat dot com
2013-05-06 11:35 ` brobecker at gnat dot com
2013-05-06 11:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-05-06 12:12 ` brobecker at gnat dot com
2013-05-10 12:10 ` cvs-commit at gcc dot gnu.org
2013-05-10 12:30 ` cvs-commit at gcc dot gnu.org
2013-05-10 12:37 ` brobecker at gnat dot com
2021-09-10 19:35 ` mehmetgelisin at aol dot com
2021-09-22 16:58 ` mervegunesli at aol dot com
2021-09-22 17:00 ` mark at klomp 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-15420-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).