From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11415 invoked by alias); 21 Sep 2015 20:56:50 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36584 Received: (qmail 26225 invoked from network); 21 Sep 2015 20:56:49 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6YbSM+WYBS6zbB0prU1yNKKnnl8X3+oQFy+oUg5m+Rs=; b=fR+09n4D2mJWRiULHThohbut4Zm+5trMtiAFXWU2VFUjw26aOd4PXQGgHtryi6u/Th PmTsZYGlMjQXzXuKtNl3yP+yJtzeiSvbRV5/ycmE+gyGUkNf2A8frPs6Eqyf51zU9Byi /L+yHgqT7rTB2SkKDVQaJ4xu7Cf+TGNzjHqrs0KHaLmOb/v4BbEMGa9ahVUXKkmuEN8a kahOKZpWIWeUsxDkbvUllEYKEOGOx/Cz0ZS5eLC+/F67HhuO1ifhVMP79MZjt3Ok1+5l STvW1ce9j4wEK+yojQDVfk2465ixDNHB+v0rApr1yJHGKL+j0kGRJqR4xMlGJZd+bU1t BlhA== X-Gm-Message-State: ALoCoQm/NhszvPwhVVMJv5lcfOYUYGbZWWDtp9w/ZKlrz8zDPu1ZnlbBRSZVkb3S+Lp/nzkB7OnX MIME-Version: 1.0 X-Received: by 10.194.87.102 with SMTP id w6mr24388691wjz.111.1442869005311; Mon, 21 Sep 2015 13:56:45 -0700 (PDT) In-Reply-To: <20150921203409.GB8913@x4> References: <20150917075759.GA24365@x4> <20150921201306.0017146b@ntlworld.com> <20150921200413.GA8913@x4> <20150921212113.74706d86@ntlworld.com> <20150921203409.GB8913@x4> Date: Mon, 21 Sep 2015 13:56:45 -0700 Message-ID: Subject: Re: Two issues found with -fsanitize=undefined From: Bart Schaefer To: Markus Trippelsdorf Cc: Peter Stephenson , Zsh hackers list Content-Type: text/plain; charset=UTF-8 On Mon, Sep 21, 2015 at 1:34 PM, Markus Trippelsdorf wrote: > > > Well, only if DEBUG is defined. And as I wrote above the issue doesn't > happen at all for -DDEBUG. You mean that even without Peter's latest patch(es), the -fsanitize checking does not report that a null pointer is being passed in the case where -DDEBUG is defined? That must mean (something along the lines of) defining DEBUG is somehow changing the behavior of malloc(0) so it returns a pointer to a zero-sized buffer rather than returning a null pointer.