Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Detect dwarf address size mismatch
Date: Tue, 17 Jul 2007 13:21:00 -0000	[thread overview]
Message-ID: <200707171301.l6HD146D020081@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070717124711.GA27936@caradoc.them.org> (message from Daniel 	Jacobowitz on Tue, 17 Jul 2007 08:47:11 -0400)

> Date: Tue, 17 Jul 2007 08:47:11 -0400
> From: Daniel Jacobowitz <drow@false.org>

Hi Daniel,

Sorry I didn't notice this before but:

> @@ -6792,6 +6793,15 @@ dwarf_decode_lines (struct line_header *
>  			     _("mangled .debug_line section"));
>  		  return;
>  		}
> +	      /* Make sure that we parsed the extended op correctly.  If e.g.
> +		 we expected a different address size than the producer used,
> +		 we may have read the wrong number of bytes.  */
> +	      if (line_ptr != extended_end)
> +		{
> +		  complaint (&symfile_complaints,
> +			     _("mangled .debug_line section"));
> +		  return;
> +		}
>  	      break;
>  	    case DW_LNS_copy:
>  	      if (lh->num_file_names < file)

The complaint "mangled .debug_line section" seems a bit unhelpful to
me, especially since there are now two identical messages for what
appears to be somewhat different conditions.  Any chance of changing
it something more distinguishable?

Mark


  reply	other threads:[~2007-07-17 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 14:19 Daniel Jacobowitz
2007-07-11 19:23 ` Eli Zaretskii
2007-07-11 19:27 ` Jim Blandy
2007-07-11 19:41   ` Daniel Jacobowitz
2007-07-11 20:30     ` Jim Blandy
2007-07-17 12:52       ` Daniel Jacobowitz
2007-07-17 13:21         ` Mark Kettenis [this message]
2007-07-17 13:55           ` Daniel Jacobowitz

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=200707171301.l6HD146D020081@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.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