Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix empty PC range psymtab<->symtab discrepancy
Date: Tue, 15 Mar 2011 15:51:00 -0000	[thread overview]
Message-ID: <m3vczk8k1q.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110314175625.GA29782@host1.jankratochvil.net> (Jan	Kratochvil's message of "Mon, 14 Mar 2011 18:56:25 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> For DW_AT_high_pc DWARF-4 has the comment
Jan> 	The high PC value may be beyond the last valid instruction in the
Jan> 	executable.
Jan> which may suggest DW_AT_low_pc == DW_AT_high_pc == 0 may be valid
Jan> and it should mean the whole address space.  I find such case
Jan> outside of the scope of this patch, such case already did not work
Jan> as the partial symtabs reading already ignored DIEs with
Jan> DW_AT_low_pc == DW_AT_high_pc.

I would not worry about this case at all.

The patch looks good to me.

Jan> +	  complaint (&symfile_complaints,
Jan> +		     _("DW_AT_low_pc %s is not < DW_AT_high_pc %s "
Jan> +		       "for DIE at 0x%x [in module %s]"),
Jan> +		     paddress (gdbarch, part_die->lowpc),
Jan> +		     paddress (gdbarch, part_die->highpc),
Jan> +		     part_die->offset, cu->objfile->name);

Thanks for putting this info into the complaint.
One of my minor wish-list items is that we would do this for all DWARF
complaints.

Tom


  reply	other threads:[~2011-03-15 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 18:16 Jan Kratochvil
2011-03-15 15:51 ` Tom Tromey [this message]
2011-03-15 16:16   ` DWARF sanity checking [Re: [patch] Fix empty PC range psymtab<->symtab discrepancy] Jan Kratochvil
2011-03-15 16:26     ` Tom Tromey

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=m3vczk8k1q.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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