From owner-freebsd-ports@FreeBSD.ORG Fri Jan 31 13:41:19 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD8E4C2C; Fri, 31 Jan 2014 13:41:19 +0000 (UTC) Received: from mail1.sysgo.com (mail1.sysgo.com [176.9.26.183]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D8531209; Fri, 31 Jan 2014 13:41:19 +0000 (UTC) Date: Fri, 31 Jan 2014 14:41:11 +0100 From: Thomas Mueller To: Dimitry Andric Subject: Re: net/avahi-app core dumps signal 11 Message-ID: <20140131144111.7a8544f1@tmu.ulm.sysgo.com> In-Reply-To: References: <1390354628.14798.7.camel@lenovo.toontown> <20140129115404.04922dd6@tmu.ulm.sysgo.com> Organization: SYSGO AG X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 13:41:19 -0000 On Fri, 31 Jan 2014 14:15:13 +0100, Dimitry Andric wrote: > On 29 Jan 2014, at 11:54, Thomas Mueller wrote: > > On Tue, 21 Jan 2014 23:37:08 -0200, Sergio de Almeida Lenzi wrote: > >> avahi-daemon dumps core, and I am unable > >> to determinw why because it aborts core just before reaching > >> the main() procedure.. > >> ========================================================= > >> > >> #0 0x0000000801304604 in pthread_testcancel () from /lib/libthr.so.3 > >> #1 0x00000008012fc706 in open () from /lib/libthr.so.3 > >> #2 0x0000000801517227 in __gets_chk () from /lib/libssp.so.0 > >> #3 0x00000008015173d2 in __chk_fail () from /lib/libssp.so.0 > >> #4 0x0000000801516ace in .init () from /lib/libssp.so.0 > >> #5 0x00007fffffffd130 in ?? () > >> #6 0x000000080061e6d1 in r_debug_state () from /libexec/ld-elf.so.1 > >> #7 0x000000080061dd57 in __tls_get_addr () from /libexec/ld-elf.so.1 > >> #8 0x000000080061c099 in .text () from /libexec/ld-elf.so.1 > >> #9 0x0000000000000000 in ?? () > >> ========================================================= > >> > >> any ideas??? > > > > Seems like a bad interaction with stack protector (libssp). > > > > I managed to get working binaries (10.0-STABLE, amd64) by adding > > --disable-stack-protector to CONFIGURE_ARGS > > Don't you think the stack protector code is trying to tell you the stack > got smashed? :-) That may well be. Then there is still the quesiotn why executables built on 9 appear to work while those built on 10 do no work. > E.g. this is most likely a real buffer overflow or something, and it > should be properly fixed, instead of removing the seat belts. Sure. -- Thomas Mueller