From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb@sources.redhat.com
Subject: pls pls point me to patch
Date: Tue, 27 Apr 2004 19:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0404271123190.22350@lazy> (raw)
I built GDB (6.1) as a 64bit binary on PPC64, when I try to debug a 64bit
threaded application I get the following.
----------------------------------------------------
GNU gdb 6.1.0.90_2004-04-27-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "powerpc64-gnu-linux"...Using host libthread_db
library "/opt/biarch/2.6/20040408_nptl/lib64/libthread_db.so.1".
(gdb) run
Starting program: /home/manjo/project/tests/tbug64
[Thread debugging using libthread_db enabled]
[New Thread 549757731856 (LWP 15225)]
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 549757731856 (LWP 15225)]
0x0000000000000000 in ?? ()
(gdb) quit
The program is running. Exit anyway? (y or n) y
-------------------------------------------------------
But I notice that this is fixed in the mainline CVS version of GDB, using
mainline version of GDB I get the following:
-------------------------------------------------------
GNU gdb 2004-04-12-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "powerpc64-gnu-linux"...Using host libthread_db
libra
ry "/opt/biarch/2.6/20040408_nptl/lib64/libthread_db.so.1".
(gdb) run
Starting program: /home/manjo/project/tests/tbug64
[Thread debugging using libthread_db enabled]
[New Thread 549757731856 (LWP 15236)]
[New Thread 549766121696 (LWP 15239)]
[New Thread 549774510304 (LWP 15240)]
tf(0): begin
tf(0): end
after create
tf(1): begin
tf(1): end
[Thread 549766121696 (LWP 15239) exited]
[Thread 549774510304 (LWP 15240) exited]
after join
Program exited normally.
(gdb) quit
[manjo@mars gdb_latest]$
----------------------------------------------------------
Can someone please point me to patch(s) that I can apply(backport) to GDB
6.1 to solve this problem. Any help is deeply appreciated.
Thanks
---
Manoj Iyer
next reply other threads:[~2004-04-27 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 19:06 Manoj Iyer [this message]
2004-04-27 23:27 ` 64/32 threaded app support Manoj Iyer
2004-04-28 16:48 ` Andrew Cagney
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=Pine.LNX.4.58.0404271123190.22350@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb@sources.redhat.com \
/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