From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9113 invoked by alias); 15 Sep 2010 07:42:19 -0000 Received: (qmail 9075 invoked by uid 48); 15 Sep 2010 07:42:06 -0000 Date: Wed, 15 Sep 2010 07:42:00 -0000 Message-ID: <20100915074206.9074.qmail@sourceware.org> From: "schwab at linux-m68k dot org" To: glibc-bugs@sources.redhat.com In-Reply-To: <20100914154213.12019.eblake@redhat.com> References: <20100914154213.12019.eblake@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/12019] memchr overshoots on Alpha X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2010-09/txt/msg00064.txt.bz2 ------- Additional Comments From schwab at linux-m68k dot org 2010-09-15 07:42 ------- (In reply to comment #1) > Stepping through the assembly reveals that the segfault is happening on: > > memchr(page-1,0,3) > > where page[-1] is '\0' and page is the start of an inaccessible page; when it > should be successfully returning page-1. This is an invalid use of memchr, see 7.1.4: If a function argument is described as being an array, the pointer actually passed to the function shall have a value such that all address computations and accesses to objects (that would be valid if the pointer did point to the first element of such an array) are in fact valid. -- http://sourceware.org/bugzilla/show_bug.cgi?id=12019 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.