From: "Frédéric RISS" <frederic.riss@gmail.com>
To: Christophe LYON <christophe.lyon@st.com>
Cc: gdb@sourceware.org
Subject: Re: GDB cannot find line info
Date: Fri, 18 Sep 2009 16:27:00 -0000 [thread overview]
Message-ID: <1253291125.5021.156.camel@funkybook> (raw)
In-Reply-To: <4AB3B14A.6000405@st.com>
Hi Christophe,
On ven., 2009-09-18 at 18:11 +0200, Christophe LYON wrote:
> 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 thought that got reported internally at ST. I'm quite sure that the
issue is Open64 not setting the is_stmt flag, and newer GDBs discarding
any line info not marked as such:
http://sourceware.org/ml/gdb-patches/2009-06/msg00633.html
Fred
next prev parent reply other threads:[~2009-09-18 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 16:12 Christophe LYON
2009-09-18 16:27 ` Frédéric RISS [this message]
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=1253291125.5021.156.camel@funkybook \
--to=frederic.riss@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