public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org
Subject: Re: [PATCH 1/2] Read DWARF5 .debug_line.
Date: Tue, 13 Oct 2020 16:19:16 +0200	[thread overview]
Message-ID: <20201013141916.GC2176@tucnak> (raw)
In-Reply-To: <20201012190649.17808-1-mark@klomp.org>

On Mon, Oct 12, 2020 at 09:06:48PM +0200, Mark Wielaard wrote:
> This handles reading DWARF5 .debug_line just like earlier DWARF versions.
> Sets file time and size to zero when not present. It skips the zero entry
> file entry (which cannot be referred to from any attribute since the value
> zero indicates that no source file), but does read the zero dir entry
> (which can be referred to from the file index). It does not yet handle
> MD5 checksums.
> 
> ChangeLog:
> 
> 	* dwz.c (get_DW_LNCT_str): New function.
> 	(skip_attr_no_dw_form_indirect): Move before read_debug_line.
> 	(read_debug_line): Handle version 5.
> ---
>  dwz.c | 611 ++++++++++++++++++++++++++++++++++++++++++++++------------
>  1 file changed, 487 insertions(+), 124 deletions(-)
> 
> diff --git a/dwz.c b/dwz.c
> index 9dbf651..9345e6c 100644
> --- a/dwz.c
> +++ b/dwz.c
> @@ -711,6 +711,28 @@ get_DW_UT_str (unsigned int ut)
>    return buf;
>  }
>  
> +/* Retrun a DW_LNCT_* name.  */

s/Retrun/Return/

> +	    case DW_LNCT_path:
> +	      if (path_ndx != -1)
> +		{
> +		  error (0, 0,
> +			 "%s: .debug_line duplicate file path elements\n",

I think no other error calls have \n at the end of the message in the whole
source (several times in the patch).

Otherwise LGTM.

	Jakub


  parent reply	other threads:[~2020-10-13 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 19:06 Mark Wielaard
2020-10-12 19:06 ` [PATCH 2/2] Write DWARF5 multifile .debug_line if possible Mark Wielaard
2020-10-13 14:23   ` Jakub Jelinek
2020-10-13 14:19 ` Jakub Jelinek [this message]
2020-10-13 21:14   ` [PATCH 1/2] Read DWARF5 .debug_line 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=20201013141916.GC2176@tucnak \
    --to=jakub@redhat.com \
    --cc=dwz@sourceware.org \
    --cc=mark@klomp.org \
    /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).