From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Script autoloading
Date: Wed, 01 Aug 2018 06:21:00 -0000 [thread overview]
Message-ID: <533925d3833ef42651918d147ccde1b6a953375b.camel@fit.cvut.cz> (raw)
Hi there,
I have a project that makes use of a shared library, say librun.so.
That library is part of the project and there's extensive python
script to support debugging.
This python script is named librun.so-gdb.py so and is located
along librun.so. Thi way. GDB loads automatically.
Works perfect, no extra setup (other autoload-safe path).
However, I struggle to make this working also on Windows, where the
library is named "librun.dll", not "librun.so'.
I thought I'd use .debug_gdb_scripts section as described in
GDB manual, but this does not work very good since $cdir is
not searched in that case.
Any idea how to make it working on both, Linux and Windows with
no additional setup (other than autoload-safe path)? What's is the
rationale for excluding $cdir from source directories when searching
for scipts?
Thanks.
Best, Jan
next reply other threads:[~2018-08-01 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 6:21 Jan Vrany [this message]
2018-08-08 14:43 ` Tom Tromey
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=533925d3833ef42651918d147ccde1b6a953375b.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=gdb@sourceware.org \
/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).