| To: | Bryan Althouse <bryan.althouse@3phoenix.com> |
|---|---|
| Subject: | Re: remote debugging: "Reply contains invalid hex digit 59" |
| From: | Daniel Jacobowitz <dan@debian.org> |
| Date: | Tue, 19 Jul 2005 10:39:11 -0400 |
| Cc: | 'Linux/MIPS Development' <linux-mips@linux-mips.org> |
| In-reply-to: | <20050719135122Z8226926-3678+3493@linux-mips.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20050719135122Z8226926-3678+3493@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.8i |
On Tue, Jul 19, 2005 at 09:52:57AM -0400, Bryan Althouse wrote: > > 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 Gdbserver doesn't have MIPS64 support merged. Assuming you're using MIPS64, as suggested by the above, then it won't work. There are patches floating around, but I haven't had time... -- Daniel Jacobowitz CodeSourcery, LLC |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: remote debugging: "Reply contains invalid hex digit 59", Alex Gonzalez |
|---|---|
| Next by Date: | Re: Updating RTC with date command, Jan-Benedict Glaw |
| Previous by Thread: | Re: remote debugging: "Reply contains invalid hex digit 59", Alex Gonzalez |
| Next by Thread: | Re: remote debugging: "Reply contains invalid hex digit 59", Maxim Osipov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |