From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6684 invoked by alias); 3 Aug 2015 18:11:57 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 6570 invoked by uid 89); 3 Aug 2015 18:11:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 03 Aug 2015 18:11:55 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E09C111A804; Mon, 3 Aug 2015 14:11:50 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zpKJIMsk9uh6; Mon, 3 Aug 2015 14:11:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B4F5829214; Mon, 3 Aug 2015 14:11:47 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 0AAC8472E6; Mon, 3 Aug 2015 11:11:46 -0700 (PDT) Date: Mon, 03 Aug 2015 18:11:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: gdb@sourceware.org Subject: Re: Isn't it OK to drop 'set write'? Message-ID: <20150803181146.GA4674@adacore.com> References: <20150726204905.GA18543@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150726204905.GA18543@host1.jankratochvil.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-08/txt/msg00000.txt.bz2 > I cannot much imagine when it is useful. For updates of too big > binaries there is gold incremental linking. Personally I have also > never considered it safe enough to use it myself, hexedit is there if > one needs to create a weird testfile. On Tru64 (which we no longer support), thread support required writing into inferior memory; so if you wanted thread support when debugging a core file, you needed to set write on. We have a couple of tests that set it unconditionally on all platforms, and it seems to have no adverse effect. Beyond that, I'm not sure. -- Joel