From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 98646 invoked by alias); 13 May 2015 14:01:18 -0000 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 Received: (qmail 98614 invoked by uid 89); 13 May 2015 14:01:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 13 May 2015 14:01:12 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id F1B5435C80A; Wed, 13 May 2015 14:01:10 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-116-27.ams2.redhat.com [10.36.116.27]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4DE16GQ004800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 May 2015 10:01:09 -0400 Date: Wed, 13 May 2015 14:01:00 -0000 From: Jan Kratochvil To: Andreas Schwab Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Fix wrong assertions Message-ID: <20150513140106.GB3023@host1.jankratochvil.net> References: <87vbg1eg08.fsf@igel.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vbg1eg08.fsf@igel.home> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00315.txt.bz2 On Sat, 09 May 2015 20:56:55 +0200, Andreas Schwab wrote: > Both callers and callees are lengths, and the sum of them can validly > equal the total length. That '<' and not '<=' was there intentional. Personally I think it needs more investigation why that can happen. The idea was that if two solutions exist neither can be perfect so there have to be some ambiguous enties so there will be '<' and not '<=' (to fit the ambiguous entries between). But creating artifical reproducers is a bit difficult and you haven't provided a reproducer so I cannot say anything much specific. Personally I do not mind, it is up to the maintainers whether the goal is just to remove the assertion or verify there aren't some other bugs causing it. Jan