linux-mips
[Top] [All Lists]

gdb problem

To: linux-mips@linux-mips.org
Subject: gdb problem
From: Maxim Osipov <maxim.osipov@gmail.com>
Date: Thu, 9 Jun 2005 17:00:22 +0400
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EZEf6e5Bm4UrkVqKx+Sz67xDOshjrMN5Opm24C4ecjwQfW4YK9+LDouJF0Juv/lTiengeQgcafUnC6tXuOT65TeJlJeOJ9GJGVe2PFPIGyyc4iz7S7HXyxynlK2s2vDXwjxR4CCLgxvFAbbPtP0kX82htPPYtBHrG13Q3lFDQyg=
Original-recipient: rfc822;linux-mips@linux-mips.org
Reply-to: maxim@mox.ru
Sender: linux-mips-bounce@linux-mips.org
Hello,

Probably a little off-topic here, but do anyone have a recipe to get
remote debugging with gdb + gdbserver working?

I have gdb-6.3 build for mips64-linux-gnu and when I try to connect
the following error appears:

/home/maxim # ./gdbserver 192.168.0.2:5339 /bin/busybox
Process /bin/busybox created; pid = 34
Listening on port 5339
Remote debugging from host 192.168.0.2
readchar: Got EOF
Remote side has terminated connection.  GDBserver will reopen the connection.
Listening on port 5339

(gdb) target remote 192.168.0.10:5339
Remote debugging using 192.168.0.10:5339
Couldn't establish connection to remote target
Reply contains invalid hex digit 59

Googling for similar problem shows, what some people also faced it,
but no solution.

Thank you,
Maxim

<Prev in Thread] Current Thread [Next in Thread>
  • gdb problem, Maxim Osipov <=