From: Jakub Jelinek <jakub@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org
Subject: Re: [PATCH] Error out on DW_AT_location with invalid encoding
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190307090227.GV7611@tucnak> (raw)
In-Reply-To: <05497c45-630c-a90f-be7a-983bb9d588eb@suse.de>
On Thu, Mar 07, 2019 at 09:59:09AM +0100, Tom de Vries wrote:
> >>> What kind of generator generates that? Ugh.
> >>
> >> AFAICT it's the result of generating a .s file from a .c file and then
> >> hand-editing the debug info (
> >> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/testsuite/gdb.dwarf2/dw2-restrict.S;h=7108b86ec109ce5a1bd299e2c36696a12024e0d5;hb=HEAD
> >> ):
> >> ...
> >> .byte 16 # DW_AT_stmt_list
> >> .byte 1 # DW_FORM_addr
> >> ...
> >
>
> Hmm, I guessed it was an error introduced by hand-editing, but digging a
> little further, it was in fact a generator error (clang 2.9):
> https://bugs.llvm.org/show_bug.cgi?id=9995 .
The patch is ok then.
Jakub
next prev parent reply other threads:[~2019-03-07 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek [this message]
2019-01-01 0:00 ` Mark Wielaard
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=20190307090227.GV7611@tucnak \
--to=jakub@redhat.com \
--cc=dwz@sourceware.org \
--cc=tdevries@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).