From: Paul Mundt <paul.mundt@timesys.com>
To: gdb@sources.redhat.com
Subject: gdbserver on PowerPC Issues
Date: Wed, 20 Nov 2002 09:18:00 -0000 [thread overview]
Message-ID: <1037812916.1315.22.camel@Origin> (raw)
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Hi,
Currently when I try and debug an application via gdbserver running on a
PowerPC target (ep8260 in this case) I get the following:
$ powerpc-linux-gdb
GNU gdb 5.2.1
Copyright 2002 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 "--host=i686-linux --target=powerpc-linux".
(gdb) file hello
Reading symbols from hello...done.
(gdb) target remote 192.168.2.84:10002
Remote debugging using 192.168.2.84:10002
0x3000fa8c in ?? ()
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
(gdb)
Now, looking through gnats, I see that someone had a similar problem and
this was logged as PR 236 -- to which there doesn't seem to be a fix.
Also looking through google, someone had suggested that this problem
might potentially be caused by having a stripped linker, and the linker
does indeed appear to be unstripped.
Any other suggestions?
Regards,
--
Paul Mundt
paul.mundt@timesys.com
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-11-20 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 9:18 Paul Mundt [this message]
2002-11-20 10:39 ` Daniel Jacobowitz
2002-11-20 11:19 ` Paul Mundt
2002-11-20 11:21 ` Daniel Jacobowitz
2002-11-20 11:29 ` Paul Koning
2002-11-20 11:45 ` Daniel Jacobowitz
2002-11-20 11:29 ` Paul Mundt
2002-11-20 12:23 ` 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=1037812916.1315.22.camel@Origin \
--to=paul.mundt@timesys.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