From: Christophe LYON <christophe.lyon@st.com>
To: gdb@sourceware.org
Subject: Re: GDB cannot find line info
Date: Fri, 25 Sep 2009 15:37:00 -0000 [thread overview]
Message-ID: <4ABCE395.1000502@st.com> (raw)
In-Reply-To: <4AB8F58A.5080405@st.com>
Hi,
I have made some progress on my problem: our compiler did not generate
the full source pathname in the Dwarf2 compile unit (it added only the
basename).
Making the compiler generate the full source pathname did fix the
regression I observed in the GDB testsuite.
I report this here because, despite investigating for quite some time, I
couldn't figure what actually confused GDB.
It looks a bit like what was already fixed by
http://sourceware.org/ml/gdb-patches/2008-04/msg00158.html
so maybe there is another inconsistency case that could be supported by GDB?
Christophe.
next prev parent reply other threads:[~2009-09-25 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- 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=4ABCE395.1000502@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