From: "H . J . Lu" <hjl@lucon.org>
To: GDB <gdb@sources.redhat.com>, binutils@sources.redhat.com
Subject: DW_CFA_def_cfa_offset_sf bug? (Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips?)
Date: Mon, 03 Jun 2002 08:55:00 -0000 [thread overview]
Message-ID: <20020603085506.A26861@lucon.org> (raw)
In-Reply-To: <20020603141808.GA24114@branoic.them.org>; from drow@mvista.com on Mon, Jun 03, 2002 at 10:18:10AM -0400
On Mon, Jun 03, 2002 at 10:18:10AM -0400, Daniel Jacobowitz wrote:
> On Sun, Jun 02, 2002 at 11:10:16PM -0700, H . J . Lu wrote:
> > On Sun, Jun 02, 2002 at 11:03:31PM -0700, H . J . Lu wrote:
> > >
> > > DW_CFA_17 is DW_CFA_offset_extended_sf, which was added to gcc on
> > > 2002-01-30. I have verifed that gcc 3.1.1 does generate it for mips.
> > > It looks like we have at least 2 bugs. First, readelf doesn't handle
> > > DW_CFA_offset_extended_sf and maybe other DAWRF debug info generated
> > > by gcc 3.1.1. Secondly, gdb 5.2 doesn't work with gcc 3.1.1 for
> > > Linux/mips.
> >
> > dwarf2cfi.c in gdb 5.2 seems to support DW_CFA_offset_extended_sf. But
> > that file is not used anywhere, at least not for Linux/x86 nor
> > Linux/mips. Did I miss something? Shouldn't we fix gdb 5.2 and
> > binutils for gcc 3.1.1?
>
> GDB doesn't need the CFA info on MIPS (although I'll try soon to let
> GDB use it). Is that really what's making GDB choke? Have you looked
> at Jakub's suggestion about gas and -gdwarf-2?
>
It has nothing to do with gas and -gdwarf-2. I used "gcc -c". I am
trying to fix readelf first. While working on DW_CFA_def_cfa_offset_sf,
I found:
case DW_CFA_def_cfa_offset_sf:
uoffset = read_uleb128 (objfile->obfd, &insn_ptr);
^^^^^^^^^^^^
fs->cfa_offset = uoffset;
/* cfa_how deliberately not set. */
break;
in dwarf2cfi.c in gdb 5.2. Shouldn't that be
case DW_CFA_def_cfa_offset_sf:
offset = read_sleb128 (objfile->obfd, &insn_ptr);
^^^^^^^^^^^^
fs->cfa_offset = offset;
/* cfa_how deliberately not set. */
break;
H.J.
next prev parent reply other threads:[~2002-06-03 15:55 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 ` H . J . Lu [this message]
[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
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=20020603085506.A26861@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--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