From: Tom Tromey <tom@tromey.com>
To: LRN <lrn1986@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Apply substitute-path to relative filenames as well
Date: Tue, 05 Mar 2019 22:24:00 -0000 [thread overview]
Message-ID: <871s3lq8fy.fsf@tromey.com> (raw)
In-Reply-To: <5a785bba-7432-f6e0-1089-5d2bdd3450a3@gmail.com> (LRN's message of "Thu, 28 Feb 2019 15:52:15 +0300")
>>>>> "LRN" == LRN <lrn1986@gmail.com> writes:
LRN> The patch is attached.
LRN> The change itself is similar to
LRN> https://www.sourceware.org/ml/gdb-patches/2017-02/msg00693.html , but the code
LRN> is slightly cleaner (at the cost of making the patch larger).
Thank you for the patch.
LRN> Also, as the patch is trivial, so i would expect it to not to require copyright
LRN> assignment (i do have one, but David Grayson might not have).
I agree.
LRN> 2019-02-28 Руслан Ижбулатов <lrn1986@gmail.com>
LRN> * source.c (find_and_open_source): Apply substitute-path to all
LRN> filenames, both absolute and relative
Is it possible to get a test case for the patch?
LRN> gdb::unique_xmalloc_ptr<char> rewritten_filename;
[...]
LRN> + rewritten_filename = rewrite_source_path (filename);
I think these two lines can now be joined; no need to have a separate
assignment.
thanks,
Tom
next prev parent reply other threads:[~2019-03-05 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:52 LRN
2019-03-05 22:24 ` Tom Tromey [this message]
2019-03-06 10:06 ` LRN
2019-03-13 12:47 ` LRN
2019-03-20 10:24 ` LRN
2019-03-27 21:36 ` Tom Tromey
2019-03-27 22:59 ` LRN
2019-03-29 20:51 ` Tom Tromey
2019-06-06 18:01 ` Tom Tromey
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=871s3lq8fy.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.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