From: Christophe LYON <christophe.lyon@st.com>
To: gdb@sourceware.org
Subject: GDB cannot find line info
Date: Fri, 18 Sep 2009 16:12:00 -0000 [thread overview]
Message-ID: <4AB3B14A.6000405@st.com> (raw)
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.
next reply other threads:[~2009-09-18 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 16:12 Christophe LYON [this message]
2009-09-18 16:27 ` Frédéric RISS
2009-09-18 16:33 ` Frederic Riss
2009-09-19 16:40 ` Joel Brobecker
2009-09-21 7:45 Robert Bu
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
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=4AB3B14A.6000405@st.com \
--to=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