From: Ian Soanes <ians@lineo.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: Linux/MIPS <linux-mips@oss.sgi.com>
Subject: Re: usermode gdb / remote gdb
Date: Wed, 25 Apr 2001 12:13:19 +0100 [thread overview]
Message-ID: <3AE6B14F.B5844932@lineo.com> (raw)
In-Reply-To: 3AE6A795.1080004@jungo.com
Michael Shmulevich wrote:
>
> Ian Soanes wrote:
>
> > The (host side) gdb I've been using was configured with ./configure
> > --target=mipsel-linux-elf (my target is an IDT MIPS 79S334 evaluation
> > board). I too am using an x86 host. I used a development version of
> > gdb-5.0 (I found the 'official' 5.0 had problems with the
> > add-symbol-file command that I use for kernel module debugging, and more
> > importantly for you... breakpoints didn't work) These problems are gone
> > in the later version.
>
> To start with, mips-linux-elf is not supported by gdbserver either with
> out-of-the-box 5.0:
>
Hi Michael,
No, I meant configuring the 'cross-debugging' gdb that I use on the x86
host. I think standard 5.0 will support the mipsel-linux-elf target also
(but something later is better). As for gdbserver... yes, you'll be out
of luck... that's why I have to hand build (cross compile) it (pending
getting the config stuff sorted out).
> $ ../../configure --target=mips-linux-elf --host=mips-linux-elf
> *** ./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-linux-elf
> checking target system type... mips-linux-elf
> checking build system type... mips-linux-elf
> checking for a BSD compatible install... (cached) /usr/bin/install -c
> configure: error: *** GDB remote does not support host mips-linux-elf
>
> Can you tell me which sources do you use?
It's actually a tar bundle that we include on one of our CDs. I think
it's a gdb snapshot dating from around August or September last year.
I'll see if I can dig out some more info and let you know. Or you could
try the latest snapshots, I haven't tried them, but they're probably OK.
>
> > Yesterday I got gdbserver working correctly on my target (over IP or
> > serial). It's a combination of Martin Rivers' mips port and my 'fixes'.
> > At this stage the build is hand cranked and neither of us have put it
> > under the control of the gdb configuration files. However, we (lineo)
> > will now start doing this.
>
> Happy to hear that you got working GDB. I hope to make one too. For
> this I need to know where to get the MIPS port and your patches.
> Can you send them to me?
>
Sure, just give me a bit of time to get something together... it's a bit
rough round the edges at the moment :)
> > I hope this helps in some way. Please let me know if there is anything I
> > can help with. It might also be worth contacting Fabrice, as it sounds
> > like he has a working gdb and gdbserver.
>
> These are indeed good news.
>
Best regards,
Ian
next prev parent reply other threads:[~2001-04-25 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 7:28 usermode gdb / remote gdb Michael Shmulevich
2001-04-25 9:36 ` Ian Soanes
2001-04-25 10:31 ` Michael Shmulevich
2001-04-25 11:13 ` Ian Soanes [this message]
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=3AE6B14F.B5844932@lineo.com \
--to=ians@lineo.com \
--cc=linux-mips@oss.sgi.com \
--cc=michaels@jungo.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