From: Tom Tromey <tom@tromey.com>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: Tom Tromey <tom@tromey.com>, "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Script autoloading
Date: Tue, 04 Sep 2018 18:22:00 -0000 [thread overview]
Message-ID: <87pnxtxgux.fsf@tromey.com> (raw)
In-Reply-To: <9076c35bc9e738f86edd401c6570955faf9565af.camel@fit.cvut.cz> (Jan Vrany's message of "Wed, 15 Aug 2018 09:09:30 +0100")
>>>>> "Jan" == Jan Vrany <jan.vrany@fit.cvut.cz> writes:
Sorry for not responding to this earlier.
Jan> Any idea how to make it working on both, Linux and Windows with
Jan> no additional setup (other than autoload-safe path)? What's is the
Jan> rationale for excluding $cdir from source directories when searching
Jan> for scipts?
[...]
Jan> Adding $cdir would solve this problem. The documentation also says:
Jan> For object files using .exe suffix GDB tries to load first the
Jan> scripts normally according to its .exe filename. But if no scripts
Jan> are found GDB also tries script filenames matching the object
Jan> file without its .exe suffix. This .exe stripping is case
Jan> insensitive and it is attempted on any platform. This makes the
Jan> script filenames compatible between Unix and MS-Windows hosts.
Jan> Maybe we can have similar automagic for .so / .dll / .dylib
Jan> extensions.
Jan> I'm ready to write a patch and submit it, unless there's a reason for
Jan> current behavior.
I couldn't think of a reason, so why not go ahead. The only risk you
have is of someone thinking of a reason during patch review,
Tom
prev parent reply other threads:[~2018-09-04 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 6:21 Jan Vrany
2018-08-08 14:43 ` Tom Tromey
2018-08-15 8:09 ` Jan Vrany
2018-09-04 18:22 ` Tom Tromey [this message]
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=87pnxtxgux.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).