This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Don't set DT_HP_DEBUG_PRIVATE in solib-pa64.c
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: mark dot kettenis at xs4all dot nl (Mark Kettenis)
- Cc: drow at false dot org, gdb-patches at sourceware dot org, randolph at tausq dot org
- Date: Wed, 6 Aug 2008 16:08:56 -0400 (EDT)
- Subject: Re: [patch] Don't set DT_HP_DEBUG_PRIVATE in solib-pa64.c
> Do you run chatr on the executable or on the shared library to do this?
Running chatr on the executable with "+dbg enable" causes all the shared
libraries used by the executable to be mapped private (except for the dynamic
loader). I've not tried it on a shared library but it looks like from
the documentation and chatr's output that this would allow private mapping
for a specific set of libraries.
> If you need to change the shared library, then I don't think this is
> the right thing to do since the user may not have write permission to
> do that.
The normal situation is to do it on the executable. If a user wanted
to use "+dbg enable" on a system library, I believe it would be possible
to copy the library and use LD_LIBRARY_PATH to select the copy. In the
32-bit runtime, this is tricker since library paths are hardcoded.
> Otherwise, I think this is ok (but perhaps the message that suggests
> using chatr can be improved).
I'll think about that.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)