Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/dwarf2] Small problem scanning line table for included files
Date: Sun, 01 Aug 2004 07:01:00 -0000	[thread overview]
Message-ID: <vt21xirjqcx.fsf@zenia.home> (raw)
In-Reply-To: <20040730211832.GW1167@gnat.com>


Joel Brobecker <brobecker@gnat.com> writes:
> > I think you are right. Looking for DW_LNS_set_file was a mistake, since
> > it is not fullproof as you demonstrated above. I looked at the dwarf3
> > (draft7) reference again, and setting that flag everytime we need to
> > record a line seems to be the perfect place to do (it's a bit
> > complicated to explain my resoning, I was concerned mostly because
> > I was a bit fuzzy on certain details which were cleared by rereding
> > the dwarf3 reference document).
> > 
> > I shall give this a try, and report back.
> 
> This worked beautifully, as expected. Here is a new patch, much simpler.
> 
> 2004-07-30  Joel Brobecker  <brobecker@gnat.com>
> 
>         * dwarf2read.c (dwarf_decode_lines): Do not consider the current
>         file as included until we record the first line in the linetable.
> 
> Tested on x86-linux with a GCC-3.4 based compiler, fixes the following
> two regressions:
> 
>         sep.exp: list using location inside included file
>         sep.exp: breakpoint inside included file
> 
> I also verified that this test still passes with GCC 3.2.
> OK to commit?

Yes, please do.  Thanks!


  reply	other threads:[~2004-08-01  7:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25 15:11 Joel Brobecker
2004-07-25 22:48 ` Michael Chastain
2004-07-28 18:56 ` Jim Blandy
2004-07-30 19:01   ` Joel Brobecker
2004-07-30 21:18     ` Joel Brobecker
2004-08-01  7:01       ` Jim Blandy [this message]
2004-08-02  1:26         ` Joel Brobecker

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=vt21xirjqcx.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.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