| To: | "'Linux/MIPS Development'" <linux-mips@linux-mips.org> |
|---|---|
| Subject: | remote debugging: "Reply contains invalid hex digit 59" |
| From: | "Bryan Althouse" <bryan.althouse@3phoenix.com> |
| Date: | Tue, 19 Jul 2005 09:52:57 -0400 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
| Thread-index: | AcWMaSsvbERBhjYxS7eDdrjjDpDV1Q== |
Is anyone doing remote debugging for mips?
I start the gdbserver on mips with:
gdbserver 192.168.2.39:2222 ./hello_loop
This produces:
Process ./hello_loop created; pid = 158
On my PC, I type:
ddd --debugger mips64-linux-gnu-gdb hello_loop
(at gdb prompt) target remote 192.168.2.55:2222
This produces:
(on gdb prompt) Couldn't establish connection to remote target
Reply contains invalid hex digit 59
(on mips) Remote debugging from host 192.168.2.39
Readchar: Got EOF
Remote side has terminated connection. GDBserver will reopen the
connection.
This problem is also described here:
http://mailman.uclinux.org/pipermail/uclinux-dev/2004-April/025421.html
Any ideas? Thanks!
Bryan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 4kc machine check, Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: Why is mmap()ed reserved memory so slow?, Ralf Baechle |
| Previous by Thread: | Updating RTC with date command, Nori, Soma Sekhar |
| Next by Thread: | Re: remote debugging: "Reply contains invalid hex digit 59", Alex Gonzalez |
| Indexes: | [Date] [Thread] [Top] [All Lists] |