From: Bob Rossi <bob@brasko.net>
To: Craig Jeffree <craig.jeffree@preston.net>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Relative source file search
Date: Mon, 10 Oct 2005 10:46:00 -0000 [thread overview]
Message-ID: <20051010104633.GA3896@white> (raw)
In-Reply-To: <1128920165.25000.56.camel@norman>
On Mon, Oct 10, 2005 at 02:56:04PM +1000, Craig Jeffree wrote:
> On Thu, 2005-10-06 at 20:25 -0400, Bob Rossi wrote:
> > Craig, you should be able to put your patch into
> > source.c:find_and_open_source in the part where it checks for
> > if (dirname != NULL)
> > {
> > ...
> > }
> >
> > instead of appending to the source_path, simply change the filename and
> > leave the source_path alone. Run this through the testsuite, are there
> > any errors?
>
> Attached is a new patch with the change in find_and_open_source. I
> haven't had any luck with the testsuite though, I kept getting a build
> error, then I did a cvs update to make sure I had the latest, now the
> whole thing won't build. Does the cvs head build today? I'm getting
I'll apply this patch and run it through the testsuite. I'll also try it
on my example and let you know what the results are.
Bob Rossi
next prev parent reply other threads:[~2005-10-10 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 7:42 Craig Jeffree
2005-10-04 1:24 ` [PATCH] " Craig Jeffree
2005-10-04 1:35 ` Daniel Jacobowitz
2005-10-06 0:57 ` Craig Jeffree
2005-10-06 2:16 ` Bob Rossi
2005-10-06 2:49 ` Craig Jeffree
2005-10-06 13:00 ` Bob Rossi
2005-10-06 23:33 ` Craig Jeffree
2005-10-07 0:25 ` Bob Rossi
2005-10-10 4:57 ` Craig Jeffree
2005-10-10 10:46 ` Bob Rossi [this message]
2005-10-10 16:46 ` Bob Rossi
2005-10-10 16:47 ` Daniel Jacobowitz
2005-10-10 23:15 ` Craig Jeffree
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=20051010104633.GA3896@white \
--to=bob@brasko.net \
--cc=craig.jeffree@preston.net \
--cc=drow@false.org \
--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