From: "Blanc, Nicolas" <nicolas.blanc@intel.com>
To: Pedro Alves <palves@redhat.com>, Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/3] remove-symbol-file
Date: Wed, 24 Apr 2013 20:40:00 -0000 [thread overview]
Message-ID: <388084C8C1E6A64FA36AD1D656E4856619DEEE98@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <8761zdow5j.fsf@fleche.redhat.com>
Thanks Tom, Pedro for your feedback.
I'll try to respond to both of you in this email.
This implementation only removes files that were added via the add-symbol-file command.
The add-symbol-file command takes as parameter the address of the text session. In this
context I think the text address is the most appropriate way to remove a file because:
1) the user knows exactly where the .text section was loaded,
2) an application can load shared libraries several times at different addresses (it's a requirement for me), and
3) I can't think of a good reason why someone would add a second symbol file at the same address.
Most likely this is a user error that should have been reported by add-symbol-file.
Note that currently in Option 4 below ADDR is in fact "objf->addr_low", but the command could be more generous
by searching first which file corresponds to ADDR and then removing it. This would be more flexible and an
alternative to Option 3, for instance.
1) remove-symbol-file FILE
2) remove-symbol-file FILE ADDR
3) remove-symbol-file -s .data DATA_ADDR
4) remove-symbol-file ADDR
As a matter of taste I prefer the options where FILE is not mandatory because this can easily be more
ambiguous.
Now as suggested by Tom, the scope of the command could also be broaden to allow removing any
symbol file. I could try to lift this restriction if you think there is more general need for removing
arbitrary symbol files.
What are your preferences?
Best Regards,
Nicolas
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2013-04-24 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:22 Nicolas Blanc
2013-04-16 11:51 ` [PATCH 2/3] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-04-24 12:18 ` Tom Tromey
2013-04-24 12:18 ` Tom Tromey
2013-04-16 12:18 ` [PATCH 1/3] Command remove-symbol-file Nicolas Blanc
2013-04-16 13:25 ` [PATCH 1/3] Added command remove-symbol-file Nicolas Blanc
2013-04-22 13:32 ` Yao Qi
2013-04-24 18:54 ` Tom Tromey
2013-04-25 19:24 ` Blanc, Nicolas
2013-04-25 20:07 ` Tom Tromey
2013-04-26 14:13 ` Yao Qi
2013-04-26 20:23 ` Pedro Alves
2013-04-30 7:30 ` Blanc, Nicolas
2013-04-30 9:28 ` Pedro Alves
2013-04-30 16:53 ` Blanc, Nicolas
2013-05-08 17:56 ` Pedro Alves
2013-05-28 11:25 ` Blanc, Nicolas
2013-04-16 14:18 ` [PATCH 3/3] Documentation for the remove-symbol-file command Nicolas Blanc
2013-04-16 15:12 ` Eli Zaretskii
2013-04-24 9:22 ` [PATCH 0/3] remove-symbol-file Tom Tromey
2013-04-24 20:40 ` Blanc, Nicolas [this message]
2013-04-24 20:49 ` Pedro Alves
2013-04-25 17:25 ` Blanc, Nicolas
2013-04-26 19:13 ` Pedro Alves
2013-04-24 17:46 ` 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=388084C8C1E6A64FA36AD1D656E4856619DEEE98@IRSMSX102.ger.corp.intel.com \
--to=nicolas.blanc@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.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