From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 31 09:06:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE99616A420 for ; Tue, 31 Jan 2006 09:06:40 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C52743D64 for ; Tue, 31 Jan 2006 09:06:39 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k0V96Ynq024795 for ; Tue, 31 Jan 2006 20:06:35 +1100 Received: from [61.8.38.79] (ppp264F.dyn.pacific.net.au [61.8.38.79]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k0V96XIp016220 for ; Tue, 31 Jan 2006 20:06:34 +1100 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <3458D5B9-860C-4185-9359-1F48FC35B048@brooknet.com.au> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hackers@freebsd.org From: Sam Lawrance Date: Tue, 31 Jan 2006 20:06:37 +1100 X-Mailer: Apple Mail (2.746.2) Subject: Which signal occurs due to a page protection violation? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 09:06:41 -0000 ElectricFence is failing during its self test on i386 7-current: Testing Electric Fence. After the last test, it should print that the test has PASSED. EF_PROTECT_BELOW= && EF_PROTECT_FREE= && EF_ALIGNMENT= && ./eftest Segmentation fault (core dumped) *** Error code 139 The program intentionally overruns and underruns buffers in order to test the functionality of ElectricFence. I think it's failing because: 1) the new jemalloc is actually catching the problem and throwing SIGSEGV 2) ElectricFence is being compiled with - DPAGE_PROTECTION_VIOLATED_SIGNAL=SIGBUS on that platform. Which signal should it be using? Does it vary across platforms and architectures? I ask this because one of the patches contains .if ${MACHINE_ARCH} == "i386" || (${MACHINE_ARCH} == "amd64" && $ {OSVERSION} < 700003) || ${MACHINE_ARCH} == "ia64" || ${MACHINE_ARCH} == "sparc64" CFLAGS+= -DPAGE_PROTECTION_VIOLATED_SIGNAL=SIGSEGV .endif