From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7886 invoked by alias); 12 Aug 2014 15:17:42 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 7877 invoked by uid 89); 12 Aug 2014 15:17:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS 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; Tue, 12 Aug 2014 15:17:40 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7CFHdBP031902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Aug 2014 11:17:39 -0400 Received: from oldenburg.str.redhat.com (ovpn-116-24.ams2.redhat.com [10.36.116.24]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s7CFHbnv009601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 12 Aug 2014 11:17:38 -0400 Message-ID: <53EA3011.4020302@redhat.com> Date: Tue, 12 Aug 2014 15:17:00 -0000 From: Florian Weimer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: William Brana CC: gcc-help@gcc.gnu.org Subject: Re: libXcursor + -finline-functions: Invalid read of size 4 References: <53E8822F.3010100@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00102.txt.bz2 On 08/12/2014 04:57 PM, William Brana wrote: >> Can you run valgrind with debugging information? It might us tell us at >> least which allocation is too short. >> >> It could be a harmless over-read from the libc string functions >> (particularly if valgrind has not been set up correctly on your system). > ==43000== at 0x89019F3: XcursorScanTheme.part.0 (library.c:137) From library.c: 137 full = malloc (strlen (dir) + 1 + strlen (subdir) + 1 + strlen (file) + 1); So this looks indeed like a strlen implementation (possibly inlined) which is not properly instrumented. -- Florian Weimer / Red Hat Product Security