From: Maxim Osipov <maxim.osipov@gmail.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Bryan Althouse <bryan.althouse@3phoenix.com>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: remote debugging: "Reply contains invalid hex digit 59"
Date: Wed, 20 Jul 2005 04:24:51 +0000 [thread overview]
Message-ID: <6097c490507192124647cd9b3@mail.gmail.com> (raw)
In-Reply-To: <20050719143911.GA3684@nevyn.them.org>
Daniel,
At the time when I was looking into this problem, I was unable to find
any patches. Could you please point me to one?
BR,
Maxim
On 7/19/05, Daniel Jacobowitz <dan@debian.org> wrote:
> 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 parent reply other threads:[~2005-07-20 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 13:52 remote debugging: "Reply contains invalid hex digit 59" Bryan Althouse
[not found] ` <1121783462.12629.10.camel@euskadi.packetvision>
2005-07-19 14:35 ` Alex Gonzalez
2005-07-19 14:36 ` Alex Gonzalez
2005-07-19 14:39 ` Daniel Jacobowitz
2005-07-20 4:24 ` Maxim Osipov [this message]
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=6097c490507192124647cd9b3@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=bryan.althouse@3phoenix.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=maxim@mox.ru \
/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.