From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: Automatically replace shared library extensions on Symbian
Date: Mon, 08 Mar 2010 18:29:00 -0000 [thread overview]
Message-ID: <20100308182840.GI3081@adacore.com> (raw)
In-Reply-To: <201003081156.00117.pedro@codesourcery.com>
> How about this? I extended the comment a bit in gdbarch.sh, avoiding
> too much target speficic info there, and described better the symbian
> specific case at the callback's call site.
Looks GREAT! :)
Thank you adding them. Just three little nits I noticed...
> +# If non-empty, this is a file extension that will be opened in place
> +# of the file extension reported by the shared library list.
> +#
> +# This is most useful for toolchains that use a post-linker tool,
> +# where the names of the files ran on the target differ in extension
^^^ run (to run, ran, run)
> +# compared to the names of the files GDB should load for debug info.
> +v:const char *:solib_symbols_extension:::::::pstring (gdbarch->solib_symbols_extension)
> + /* On this target, the toolchain outputs ELF files, with `sym' for
> + filename extension (e.g., `FOO.sym'); these are post-linker
> + processed into PE-ish DLLs (e.g., `FOO.dll'), and its these that
^^^ it's
> + are actually copied to and ran on the target. Naturally, when
^^^ run
> + listing shared libraries, Symbian stubs report the DLL filenames.
> + Setting this makes it so that GDB automatically looks for the
> + corresponding ELF files on the host's filesystem. */
--
Joel
next prev parent reply other threads:[~2010-03-08 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 18:46 Pedro Alves
2010-03-08 4:54 ` Joel Brobecker
2010-03-08 11:56 ` Pedro Alves
2010-03-08 18:29 ` Joel Brobecker [this message]
2010-03-08 19:31 ` Pedro Alves
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=20100308182840.GI3081@adacore.com \
--to=brobecker@adacore.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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