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 04:54:00 -0000 [thread overview]
Message-ID: <20100308045415.GB3081@adacore.com> (raw)
In-Reply-To: <201003051846.23406.pedro@codesourcery.com>
> What do you think of this?
A gdbarch setting sounds indeed better to me, as the debugger is then
doing the right thing automatically.
> 2010-03-05 Daniel Jacobowitz <dan@codesourcery.com>
> Pedro Alves <pedro@codesourcery.com>
>
> gdb/
> * solib.c (solib_find): Replace extension if
> solib_symbols_extension set in the target gdbarch.
> * arm-symbian-tdep.c (arm_symbian_init_abi): Set
> solib_symbols_extension to "sym".
> * gdbarch.sh (solib_symbols_extension): New variable.
> (pstring): New function.
> * gdbarch.h, gdbarch.c: Regenerate.
No real comment on the code, except maybe:
> +
> +# If non-empty, this is a file extension that will be opened in place
> +# of the file extension reported by the shared library list.
> +v:const char *:solib_symbols_extension:::::::pstring (gdbarch->solib_symbols_extension)
Would you mind expanding the commend above to explain that Symbian OS
is one example where this can be useful, and why? Basically, the current
description is a bit short, and I also found the paragraph describing
what happens on Symbian to be very interesting and useful...
Another option for preserving the description of what happens on Symbian OS
is to provide it at the location where you call set_solib_symbols_extension,
but it might be more difficult for someone working on a different architecture
having the same problem and looking for the gdbarch method that would allow
him to solve his problem?
--
Joel
next prev parent reply other threads:[~2010-03-08 4:54 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 [this message]
2010-03-08 11:56 ` Pedro Alves
2010-03-08 18:29 ` Joel Brobecker
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=20100308045415.GB3081@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