From: Jun Sun <jsun@mvista.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: Ian Soanes <ians@lineo.com>, Linux/MIPS <linux-mips@oss.sgi.com>,
FR Linux/MIPS <linux-mips@fnet.fr>
Subject: Re: usermode gdb / remote gdb
Date: Mon, 30 Apr 2001 10:40:35 -0700 [thread overview]
Message-ID: <3AEDA393.653FD026@mvista.com> (raw)
In-Reply-To: 3AEBE34C.5070009@jungo.com
Michael Shmulevich wrote:
>
> Jun,
>
> I have a problem with your patch:
>
> Jun Sun wrote:
>
> > --- gdb-4.17/gdb/config/mips/mipsel-linux.mh.orig Mon May 22 18:39:07 2000
> > +++ gdb-4.17/gdb/config/mips/mipsel-linux.mh Mon May 22 18:39:07 2000
>
> Gdb seems to miss those files from the distribution. I have checked out
> its CVS tree, and this is what I got:
>
> [michaels@kobie mips]$ pwd
> /home/michaels/CVS/gdb/gdb/config/mips
> [michaels@kobie mips]$ ls
> CVS/ irix5.mh nm-mips.h tm-mips.h
> tm-vr5000el.h vxmips.mt
> bigmips.mt irix5.mt nm-news-mips.h tm-mips64.h tm-vxmips.h
> wince.mt
> bigmips64.mt littlemips.mh nm-riscos.h tm-mipsm3.h tm-wince.h
> xm-irix3.h
> decstation.mh littlemips.mt riscos.mh tm-mipsv4.h tx39.mt
> xm-irix4.h
> decstation.mt mipsm3.mh tm-bigmips.h tm-tx39.h tx39l.mt
> xm-irix5.h
> embed.mt mipsm3.mt tm-bigmips64.h tm-tx39l.h vr4100.mt
> xm-mips.h
> embed64.mt mipsv4.mh tm-embed.h tm-vr4100.h vr4300.mt
> xm-mipsm3.h
> embedl.mt mipsv4.mt tm-embed64.h tm-vr4300.h vr4300el.mt
> xm-mipsv4.h
> embedl64.mt news-mips.mh tm-embedl.h tm-vr4300el.h vr4xxx.mt
> xm-news-mips.h
> irix3.mh nm-irix3.h tm-embedl64.h tm-vr4xxx.h vr4xxxel.mt
> xm-riscos.h
> irix3.mt nm-irix4.h tm-irix3.h tm-vr4xxxel.h vr5000.mt
> irix4.mh nm-irix5.h tm-irix5.h tm-vr5000.h vr5000el.mt
> [michaels@kobie mips]$ ls -l *linux*
> ls: *linux*: No such file or directory
> [michaels@kobie mips]$ cat CVS/Root
> :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src
> [michaels@kobie mips]$
>
> So, as I said, there seems to be no support for mips-linux in GDB tree.
> Where can I get the gdb-4.17 you were talking about?
>
You can probably look around and find the official gdb-4.17 release.
A better bet is to get from the mvista CDK 1.2 release:
ftp://ftp.mvista.com/pub/CDKit/1.2/cd/Source/SRPMS/hhl-gdb-5.0-1.src.rpm
It says gdb 5.0, but I think gdb-4.17 is "embedded" in it. (If not, let me
know).
If you try to add linux-mips to gdb 5.0, you might want to look into the new
multi-arch structure introduced in gdb 5.0. It *might* be the reason why
original MIPS stuff is removed.
Good luck.
Jun
next prev parent reply other threads:[~2001-04-30 17:47 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
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 18:05 ` Michael Shmulevich
2001-04-26 17:03 ` Jun Sun
2001-04-29 9:47 ` Michael Shmulevich
2001-04-30 17:40 ` Jun Sun [this message]
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=3AEDA393.653FD026@mvista.com \
--to=jsun@mvista.com \
--cc=ians@lineo.com \
--cc=linux-mips@fnet.fr \
--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 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.