From: Simon Marchi <simon.marchi@polymtl.ca>
To: Ali Tamur <tamur@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] DWARF 5 support: Handle line table and file indexes
Date: Mon, 21 Oct 2019 20:07:00 -0000 [thread overview]
Message-ID: <e4687ab5-8cfb-9843-59b3-d17532faa3d6@polymtl.ca> (raw)
In-Reply-To: <20191021194749.159923-1-tamur@google.com>
On 2019-10-21 3:47 p.m., Ali Tamur wrote:
>> Update the comment for psymtab_include_file_name
> Done.
>
>> is_valid_file_index should be a method of line_header
> Done.
> ---
>
> * Fix handling of file and directory indexes in line tables; in DWARF 5 the
> indexes are zero-based. Make file_names field private to abstract this detail
> from the clients. Introduce file_names, is_valid_file_index and
> file_names_size methods. Reflect these changes in clients.
> * Handle DW_FORM_data16 in read_formatted_entries; it is used to record MD5
> of the file entries in DWARF 5.
> * Fix a bug in line header parsing that calculates the length of the header
> incorrectly. (Seemingly this manifests itself only in DWARF 5).
>
> Tested with CC=/usr/bin/gcc (version 8.3.0) against master branch (also with
> -gsplit-dwarf and -gdwarf-4 flags) and there was no increase in the set of
> tests that fails. (gdb still cannot debug a 'hello world' program with DWARF 5,
> so for the time being, this is all we care about).
>
> This is part of an effort to support DWARF 5 in gdb.
Thanks, this version LGTM, please push.
Simon
prev parent reply other threads:[~2019-10-21 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 4:53 Ali Tamur via gdb-patches
2019-10-02 1:52 ` Ali Tamur via gdb-patches
2019-10-08 1:05 ` Ali Tamur via gdb-patches
2019-10-10 3:14 ` Simon Marchi
2019-10-15 20:19 ` Ali Tamur via gdb-patches
2019-10-16 3:04 ` Simon Marchi
2019-10-18 19:31 ` Ali Tamur via gdb-patches
2019-10-21 5:55 ` Simon Marchi
2019-10-21 19:47 ` Ali Tamur via gdb-patches
2019-10-21 20:07 ` Simon Marchi [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=e4687ab5-8cfb-9843-59b3-d17532faa3d6@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tamur@google.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