From: <oparz@compuserve.de>
To: linuxppc-embedded@ozlabs.org
Subject: gdb/gdbserver TQM885
Date: Sat, 17 Feb 2007 20:56:44 +0100 [thread overview]
Message-ID: <3efc373ef4e6.3ef4e63efc37@compuserve.de> (raw)
Hello,
I have a problem on debugging my target board TQM885 (ELDK, Linux
2.4.25) with gdb/gdbserver . My Testprogram is a simple helloworld. The
program itself is running as expected, but its not possible to debug.
Would be very glad, if anyone can help me. Target and Host are in
different subnets, but this is solved via route add.. command
___________________
Host running gdb:
oparz@linux:~/autoconf_tests/hello_GNU-0.1> gdb ./hello_GNU
GNU gdb 6.3
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 "i586-suse-linux"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".
(gdb) target remote 192.168.10.232:5000
Remote debugging using 192.168.10.232:5000
Couldn't establish connection to remote target
Remote sent bad register number 40: 3000ef14;
Packet: 'T0501:7ffffed0;40:3000ef14;'
(gdb)
__________________________
and the target running gdbserver:
root@/># gdbserver 192.168.2.21:5000 ./hello_GNU
Process ./hello_GNU created; pid = 56
Remote debugging from host 192.168.2.21
readchar: Got EOF
Remote side has terminated connection. GDBserver will reopen the
connection.
__________________
Any help is very appreciated
Dr. Otto Parzhuber
Munich University of Applied Sciences
Fac. of Precision Engineering
next reply other threads:[~2007-02-17 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 19:56 oparz [this message]
2007-02-17 22:12 ` gdb/gdbserver TQM885 Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-02-18 8:32 oparz
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=3efc373ef4e6.3ef4e63efc37@compuserve.de \
--to=oparz@compuserve.de \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.