From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3513 invoked by alias); 18 Apr 2012 14:37:20 -0000 Received: (qmail 3483 invoked by uid 22791); 18 Apr 2012 14:37:19 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 18 Apr 2012 14:37:01 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q3IEaiYc013819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 18 Apr 2012 10:36:44 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q3IEahOs024472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 18 Apr 2012 10:36:43 -0400 From: Tom Tromey To: Pedro Alves Cc: Doug Evans , Joel Brobecker , gdb-patches Subject: Re: [RFA] Ensure result of make_cleanup is never NULL. References: <20120416144011.GH2852@adacore.com> <4F8C3350.1030601@redhat.com> <4F8E88E3.1010900@redhat.com> <4F8ECE4F.1070004@redhat.com> Date: Wed, 18 Apr 2012 14:38:00 -0000 In-Reply-To: <4F8ECE4F.1070004@redhat.com> (Pedro Alves's message of "Wed, 18 Apr 2012 15:23:11 +0100") Message-ID: <87sjg1qf7o.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-04/txt/msg00576.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> Well, aren't all places using the sentinel, using it throught the macro? Pedro> What does this make more robust? If you initialize the object it can end up in a read-only section, so writes to it will SEGV. In this particular case I don't see that this would help a lot, since the object is just a sentinel. But, it wouldn't hurt and maybe it would catch some really unusual bug. Tom