From: Tom Tromey <tom@tromey.com>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Script autoloading
Date: Wed, 08 Aug 2018 14:43:00 -0000 [thread overview]
Message-ID: <87pnysapi8.fsf@tromey.com> (raw)
In-Reply-To: <533925d3833ef42651918d147ccde1b6a953375b.camel@fit.cvut.cz> (Jan Vrany's message of "Wed, 01 Aug 2018 07:21:20 +0100")
>>>>> "Jan" == Jan Vrany <jan.vrany@fit.cvut.cz> writes:
Jan> However, I struggle to make this working also on Windows, where the
Jan> library is named "librun.dll", not "librun.so'.
Jan> I thought I'd use .debug_gdb_scripts section as described in
Jan> GDB manual, but this does not work very good since $cdir is
Jan> not searched in that case.
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?
I don't know why $cdir isn't searched, other than what the manual says:
If the entry specifies a file, GDB will look for the file first in the
current directory and then along the source search path (*note
Specifying Source Directories: Source Path.), except that '$cdir' is not
searched, since the compilation directory is not relevant to scripts.
This doesn't really explain it to me, though, since the compilation
directory is used to find sources.
Why can't you just rename the file at install time, depending on what
the library is called? It seems like your build system is already doing
that for the library itself.
Tom
next prev parent reply other threads:[~2018-08-08 14:43 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 [this message]
2018-08-15 8:09 ` Jan Vrany
2018-09-04 18:22 ` 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=87pnysapi8.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).