From: "gui" <guijian@ict.ac.cn>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com <gdb@sources.redhat.com>
Subject: Re: how to build native GDB on mips64 linux ?
Date: Wed, 24 Mar 2004 13:10:00 -0000 [thread overview]
Message-ID: <20040324131000.5klo-jc-QbjnyjmBNSOavwBhDuTK-STRiP1CGKyl4rI@z> (raw)
When I tried debugging a mips64/Linux target with i686/Linux host, I
got the following results:
[gdbserver side]
$> ./gdbserver 200.121.3.185:6001 matrix_rev
Listening on port 6001
Remote debugging from host 200.121.3.185
readchar: Got EOF
Remote side has terminated connection. GDBserver will reopen the connection.
[gdb side]
$> ./gdb matrix_rev
GNU gdb 6.0.90_2004-03-19-cvs
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 "--host=i686-pc-linux-gnu --target=mips64el-linux"...
(gdb) target remote 200.121.3.191:6001
Remote debugging using 200.121.3.191:6001
Couldn't establish connection to remote target
Reply contains invalid hex digit 59
gdbserver was configured for mips64el-linux. gdbserver and the debugged program were both compiled with cross gcc 3.3 (mips64el-linux-gcc -mabi=64 -static) on i686/Linux host.
"file matrix_rev" gives the following information: ELF 64-bit LSB MIPS-III executable, MIPS, version 1 (SYSV), for GNU/Linux 2.4.0, statically linked, not stripped.
Could you give more advice ?
Thanks.
======= 2004-03-23 14:25:00 Daniel Jacobowitz wrote: =======
>On Tue, Mar 23, 2004 at 09:30:42AM +0800, guijian wrote:
>> Thanks for your attention.
>>
>> Then, can I use gdb to remote-debug or core-debug a mips64/Linux target
>> with i686/Linux host?
>
>Yes. In 6.1, gdbserver _should_ work. It is lightly tested.
>
>> Is there any plan to port native mips64/Linux GDB? If such a port does not
>> exist, could someone give me some advice where I can start it myself?
>
>I'm working on it, on and off. I have some more things to fix for
>32-bit MIPS GNU/Linux first.
>
>--
>Daniel Jacobowitz
>MontaVista Software Debian GNU/Linux Developer
>
>.
= = = = = = = = = = = = = = = = = = = =
gui
next reply other threads:[~2004-03-24 9:25 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 13:10 gui [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-24 13:10 gui
2004-03-22 17:48 Daniel Jacobowitz
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
2004-03-22 14:22 guijian
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=20040324131000.5klo-jc-QbjnyjmBNSOavwBhDuTK-STRiP1CGKyl4rI@z \
--to=guijian@ict.ac.cn \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox