From: Joel Brobecker <brobecker@adacore.com>
To: Christophe LYON <christophe.lyon@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] obvious pattern fix in gdb.base/step-line.exp
Date: Mon, 30 Mar 2009 18:23:00 -0000 [thread overview]
Message-ID: <20090330170216.GB9472@adacore.com> (raw)
In-Reply-To: <49D083FB.6020108@st.com>
> So... it may be an issue with my compiler handling of #line?
Not quite sure from the dump what exactly causes the change of behavior,
I would need to look at the code more precisely, and I'm a little rush
right now.
But since I believe that printing the full name is perfectly valid (in
fact, I later verified that this is what happens with Ada files as well,
even though the debug info looks similar to what we get with step-line.c),
it's fine to commit your patch.
--
Joel
next prev parent reply other threads:[~2009-03-30 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 14:05 Christophe LYON
2009-03-27 18:53 ` Joel Brobecker
2009-03-30 13:51 ` Christophe LYON
2009-03-30 18:23 ` Joel Brobecker [this message]
2009-03-31 15:25 ` Christophe LYON
2009-04-01 18:32 ` Joel Brobecker
2009-04-02 8:52 ` Christophe LYON
2009-04-17 17:07 ` Christophe LYON
2009-04-17 17:30 ` Daniel Jacobowitz
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=20090330170216.GB9472@adacore.com \
--to=brobecker@adacore.com \
--cc=christophe.lyon@st.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