From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/dwarf] Handle debug_line extended ops correctly
Date: Wed, 16 Jun 2004 17:16:00 -0000 [thread overview]
Message-ID: <20040616171606.GA30668@nevyn.them.org> (raw)
In-Reply-To: <vt28yenxwh9.fsf@zenia.home>
On Wed, Jun 16, 2004 at 12:07:30PM -0500, Jim Blandy wrote:
> Daniel Jacobowitz <drow@false.org> writes:
>
> > This has been hanging around in my tree for a while. The HP-UX ia64
> > compiler generates things like this in .debug_line:
> > Extended opcode 32: UNKNOWN: length 51
> > Extended opcode 32: UNKNOWN: length 146
> >
> > 146 is different as a byte and as a uleb128, so we get confused. Of course,
> > we're going to bail out shortly anyway because we don't accept unknown
> > extended ops (probably for the best); but we might as well parse the length
> > right.
> >
> > OK?
>
> Okay.
Committed, thanks.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-06-16 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 15:44 Daniel Jacobowitz
2004-06-16 17:07 ` Jim Blandy
2004-06-16 17:16 ` Daniel Jacobowitz [this message]
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=20040616171606.GA30668@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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