Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Robert Bu <robert.bu@gmail.com>
To: christophe.lyon@st.com
Cc: gdb@sourceware.org
Subject: Re: GDB cannot find line info
Date: Mon, 21 Sep 2009 07:45:00 -0000	[thread overview]
Message-ID: <a0319f700909210045q4b674e77tfee6b082babe379@mail.gmail.com> (raw)

Hi Christophe,

Maybe you can try the CVS head or the 7.0 preview. I've once met the
same problem. And the problem is gone in CVS. Actually the problem is
fixed by the newly added function "watch_main_source_file_lossage
(void)" in buildsym.c

Robert.

>
>
> Hello,
>
> I have found a bug in our compiler (Open64 for ST200), which I have
> fixed to make it correctly output the directory table related to
> debug_line info.
> But now, I have many regressions in the GDB testsuite (6.8), the first
> one being in break.exp: now the command "break break.c:103" returns
> 'No line 103 in file "break.c"'
>
> I have dumped the dwarf debug_line info with 'dwarfdump -l' and
> 'readelf -wl', but could not find anything suspect:
> - with dwarfdump, the only difference is in the directory path
> - with readelf, the directory tables contain one more entry (absolute
> path to gdb.base) and the file table has dir numbers updated
> accordingly. (obviously, the length and offset of the corresponding
> sections are different)
>
> Is there any GDB internal command I could use to understand the problem?
>
> Thanks,
>
> Christophe.
>


             reply	other threads:[~2009-09-21  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  7:45 Robert Bu [this message]
2009-09-21 15:00 ` Christophe LYON
2009-09-21 15:35   ` Christophe LYON
2009-09-22 16:04     ` Christophe LYON
2009-09-25 15:37       ` Christophe LYON
  -- strict thread matches above, loose matches on Subject: below --
2009-09-18 16:12 Christophe LYON
2009-09-18 16:27 ` Frédéric RISS
2009-09-18 16:33   ` Frederic Riss
2009-09-19 16:40 ` 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=a0319f700909210045q4b674e77tfee6b082babe379@mail.gmail.com \
    --to=robert.bu@gmail.com \
    --cc=christophe.lyon@st.com \
    --cc=gdb@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