From: Daniel Jacobowitz <drow@mvista.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Eric Christopher <echristo@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
binutils@sources.redhat.com, GDB <gdb@sources.redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Use stabs for Linux/mips (Re: binutils is broken on ELF/MIPS)
Date: Mon, 03 Jun 2002 18:40:00 -0000 [thread overview]
Message-ID: <20020604014000.GA3798@branoic.them.org> (raw)
In-Reply-To: <20020603180351.A3594@lucon.org>
On Mon, Jun 03, 2002 at 06:03:51PM -0700, H . J . Lu wrote:
> On Mon, Jun 03, 2002 at 05:48:14PM -0700, Eric Christopher wrote:
> >
> > > I tried a dirty, quick change enclosed. I still can't use gdb 5.2 to
> > > debug gcc 3.1.1 on Linux/mipsel. I don't think it is a good idea to
> > > make gcc 3.1.1 generate unusable debug info by default..
> > >
> >
> > Definitely not a huge fan of that patch. I have another one from Matt
> > Green (attached) that I'm not ecstatic about either, but also seems to
> > work. The correct answer is to make dwarf-2 work under mips. It may
> > require some reworking though.
> >
>
> Does it really make dwarf-2 work? Does it break MIPS_STABS_ELF?
It should, without breaking or affecting MIPS_STABS_ELF at all.
Eric, why don't you like it - or rather, what else do you think "making
dwarf-2 work under MIPS" means? I think that was the only missing
detail.
(2.13 is on the horizon already; I'd really like this fixed)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-04 1:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 14:36 Does gdb 5.2 support gcc 3.1.1 on Linux/mips? H . J . Lu
2002-06-02 18:00 ` Daniel Jacobowitz
2002-06-02 19:43 ` H . J . Lu
2002-06-02 22:01 ` Daniel Jacobowitz
2002-06-02 22:05 ` H . J . Lu
2002-06-02 22:09 ` Daniel Jacobowitz
2002-06-02 22:42 ` H . J . Lu
2002-06-02 23:03 ` H . J . Lu
2002-06-02 23:10 ` H . J . Lu
2002-06-03 4:22 ` Daniel Berlin
2002-06-03 7:18 ` Daniel Jacobowitz
2002-06-03 8:55 ` DW_CFA_def_cfa_offset_sf bug? (Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips?) H . J . Lu
[not found] ` <20020603092959.A27426@lucon.org>
[not found] ` <20020603104131.A28590@lucon.org>
[not found] ` <20020603115703.A29881@lucon.org>
[not found] ` <20020604003246.C20867@sunsite.ms.mff.cuni.cz>
[not found] ` <20020603153716.A1294@lucon.org>
2002-06-03 16:25 ` PATCH: Use stabs for Linux/mips (Re: binutils is broken on ELF/MIPS) H . J . Lu
2002-06-03 16:41 ` Daniel Jacobowitz
2002-06-03 16:51 ` H . J . Lu
2002-06-03 17:43 ` Richard Henderson
2002-06-03 19:52 ` Doug Evans
2002-06-03 19:54 ` H . J . Lu
2002-06-03 20:36 ` Richard Henderson
2002-06-03 17:50 ` Eric Christopher
2002-06-03 18:03 ` H . J . Lu
2002-06-03 18:29 ` Eric Christopher
2002-06-03 19:47 ` H . J . Lu
2002-06-03 18:40 ` Daniel Jacobowitz [this message]
2002-06-03 19:51 ` H . J . Lu
2002-06-03 20:23 ` Daniel Jacobowitz
2002-06-03 20:28 ` H . J . Lu
2002-06-04 13:18 ` Eric Christopher
2002-06-02 23:30 ` Does gdb 5.2 support gcc 3.1.1 on Linux/mips? Jakub Jelinek
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=20020604014000.GA3798@branoic.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=jakub@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