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: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: dave at hiauly1 dot hia dot nrc dot ca
- Cc: dave at hiauly1 dot hia dot nrc dot ca, drow at false dot org, gdb-patches at sourceware dot org, randolph at tausq dot org
- Date: Wed, 6 Aug 2008 21:48:24 +0200 (CEST)
- Subject: Re: [patch] Don't set DT_HP_DEBUG_PRIVATE in solib-pa64.c
- References: <20080806192413.ABC03431A@hiauly1.hia.nrc.ca>
> Date: Wed, 6 Aug 2008 15:24:12 -0400 (EDT)
> From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>
> Hi,
>
> > One thing that I have noticed is that the shared libraries are always
> > forced private which makes them writeable. I recently had a program
> > which dropped core when the library code was shared but not when they
> > were private.
>
> The patch below implements my suggestion to not set DT_HP_DEBUG_PRIVATE
> in solib-pa64.c as the user can do this with chatr (or pxdb). Tested
> on hppa2.0w-hp-hpux11.11.
Do you run chatr on the executable or on the shared library to do this?
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.
Otherwise, I think this is ok (but perhaps the message that suggests
using chatr can be improved).
Mark