From: Michael Shmulevich <michaels@jungo.com>
To: FR Linux/MIPS <linux-mips@fnet.fr>, Linux/MIPS <linux-mips@oss.sgi.com>
Subject: usermode gdb / remote gdb
Date: Wed, 25 Apr 2001 10:28:58 +0300 [thread overview]
Message-ID: <3AE67CBA.4060606@jungo.com> (raw)
Hi,
I am trying to configure gdb to debug usermode on my mips box. i have
two choices: one is to use "native"-compiled gdb, ot remote debugging on
x86 box via serial or IP.
Currently I have no luck making any of the two configurations.
For "native" gdb I try to
$ CC=mips-linux-gcc ./configure mips-linux
and eventually I get
configure: error: *** Gdb does not support host mips-mips-linux-gnu
For remote debugging, I use
$ ./configure --target=mips
which succeded, and I even am able to get cross 'mips-gdb' which
understands mips executables. However, when trying to configure gdbserver,
$ cd gdb/gdbserver
$ ../../configure mips-linux
*** ./configure.in has no "per-host:" line.
*** Hmm, looks like this directory has been autoconfiscated.
*** Running the local configure script.
creating cache config.cache
checking host system type... mips-mips-linux-gnu
checking target system type... mips-mips-linux-gnu
checking build system type... mips-mips-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
configure: error: *** GDB remote does not support host mips-mips-linux-gnu
Too bad, have seen it before, so I just tried to
$ ../../configure --host=mips --target=mips
*** ./configure.in has no "per-host:" line.
*** Hmm, looks like this directory has been autoconfiscated.
*** Running the local configure script.
loading cache config.cache
checking host system type... mips-mips-elf
checking target system type... mips-mips-elf
checking build system type... mips-mips-elf
checking for a BSD compatible install... /usr/bin/install -c
configure: error: *** GDB remote does not support host mips-mips-elf
And the last try (like the one that worked before):
$ ../../configure --target=mips
Configuring for a i686-pc-linux-gnu host.
*** ./configure.in has no "per-host:" line.
*** Hmm, looks like this directory has been autoconfiscated.
*** Running the local configure script.
loading cache config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... mips-mips-elf
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
updating cache config.cache
creating ./config.status
creating Makefile
linking ./../config/i386/xm-linux.h to xm.h
linking ./../config/mips/tm-embed.h to tm.h
linking ./../config/nm-empty.h to nm.h
which clearly misconfigured, because of host system type set to x86, and
nm.h is pointing to nm-emty.h (?).
From what I see, I cannot use neither mips-linux nor mips-elf for host
specification. On the other hand, I have seen lately a lot of discussion
for gdb support for MIPS (bot kernel and usermode).
I just wonder what I am missing from all this story.
Your help is greatly appreciated.
Sincerely yours,
Michael Shmulevich
______________________________________
Software Developer
Jungo - R&D
email: michaels@jungo.com
web: http://www.jungo.com
Phone: 1-877-514-0537(USA) +972-9-8859365(Worldwide) ext. 233
Fax: 1-877-514-0538(USA) +972-9-8859366(Worldwide)
next reply other threads:[~2001-04-25 7:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 7:28 Michael Shmulevich [this message]
2001-04-25 9:36 ` usermode gdb / remote gdb Ian Soanes
2001-04-25 10:31 ` Michael Shmulevich
2001-04-25 11:13 ` Ian Soanes
2001-04-25 17:39 ` Jun Sun
2001-04-26 4:04 ` Ralf Baechle
2001-05-02 14:12 ` Maciej W. Rozycki
2001-04-26 18:05 ` Michael Shmulevich
2001-04-26 17:03 ` Jun Sun
2001-04-26 18:05 ` Michael Shmulevich
2001-04-29 9:47 ` Michael Shmulevich
2001-04-30 17:40 ` Jun Sun
2001-05-07 20:40 ` Wayne Gowcher
2001-05-07 20:40 ` Wayne Gowcher
2001-04-25 15:02 ` serial console, have linefeed but no command prompt Wayne Gowcher
2001-04-25 17:25 ` Pete Popov
2001-04-25 18:38 ` Wayne Gowcher
2001-04-25 19:50 ` Scott A McConnell
2001-04-27 15:40 ` load_elf_binary problems ? Wayne Gowcher
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=3AE67CBA.4060606@jungo.com \
--to=michaels@jungo.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.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