From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4042 invoked by alias); 6 Aug 2008 19:49:14 -0000 Received: (qmail 4033 invoked by uid 22791); 6 Aug 2008 19:49:13 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 19:48:36 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id m76JmP8N026068; Wed, 6 Aug 2008 21:48:25 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id m76JmOdf028185; Wed, 6 Aug 2008 21:48:24 +0200 (CEST) Date: Wed, 06 Aug 2008 19:49:00 -0000 Message-Id: <200808061948.m76JmOdf028185@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: dave@hiauly1.hia.nrc.ca CC: dave@hiauly1.hia.nrc.ca, drow@false.org, gdb-patches@sourceware.org, randolph@tausq.org In-reply-to: <20080806192413.ABC03431A@hiauly1.hia.nrc.ca> (dave@hiauly1.hia.nrc.ca) Subject: Re: [patch] Don't set DT_HP_DEBUG_PRIVATE in solib-pa64.c References: <20080806192413.ABC03431A@hiauly1.hia.nrc.ca> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00136.txt.bz2 > Date: Wed, 6 Aug 2008 15:24:12 -0400 (EDT) > From: "John David Anglin" > > 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