From owner-freebsd-arm@FreeBSD.ORG Fri Apr 5 11:20:05 2013 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3BE70950; Fri, 5 Apr 2013 11:20:05 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 79850FAA; Fri, 5 Apr 2013 11:20:04 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id u12so2788444wey.5 for ; Fri, 05 Apr 2013 04:20:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=ICStAGpqmZEWTSuM3ZyF1QwEsWl7RnTMgCd78hiKY3s=; b=wqdKrULIXRHxRvN0+cNeWB4LHqLK3QS25LsterR2QPlpcR/9XFB4eiiCiPsbrxFEZF PvSGc7Sc78qt2nwXDWWylEz8U3PS9me0cdkV09JRTzaIp5stlz89kOnpKG/aGKeeaG8K k6wb0uDcGkZMwV9yFYm16SkTP8YNOtnvYcD+UPIuGQywwNT7hbzMhbWyGtTwhZwfH41T DyfJcAmrglOsfpHtWP5JeNmxLSm1BRcVb6MIYapD4/84gVkzSZfmMdCI+2iC+ktwoP/Q UNJC49JVXWWAhwNH0SvcsC+yu+AmmlDxvVAeMO0peR/+vK8aTL0fwLuWUlLTD3J6OdVb AHjg== X-Received: by 10.194.92.231 with SMTP id cp7mr15600100wjb.19.1365160394955; Fri, 05 Apr 2013 04:13:14 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:8ee:b906:943e:e71d? ([2001:980:d7ed:1:8ee:b906:943e:e71d]) by mx.google.com with ESMTPS id fg6sm3442134wib.10.2013.04.05.04.13.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 04:13:13 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <515EB1C8.3050708@freebsd.org> Date: Fri, 05 Apr 2013 13:13:12 +0200 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130403 Thunderbird/17.0.5 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: signal 11 after kernel update r247742 -> r248706 References: <51545932.9050901@freebsd.org> <1364484652.36972.81.camel@revolution.hippie.lan> <515466B5.4020403@freebsd.org> <5155BC1C.2000104@freebsd.org> <515D7E0A.6010504@freebsd.org> <515D9239.40606@freebsd.org> In-Reply-To: <515D9239.40606@freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: arm@freebsd.org, Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2013 11:20:05 -0000 On 04-04-2013 16:46, René Ladan wrote: > On 04-04-2013 15:20, René Ladan wrote: >> On 29-03-2013 18:58, Adrian Chadd wrote: >>> On 29 March 2013 09:06, René Ladan >> > wrote: >>> >>> >>> >> I'm at r248509 on my rpi and everything is good; maybe that'll help >>> >> narrow the binary search. >>> > Ok, I'll start looking from there. >>> >>> The 'skeleton' unmapped IO commit was r248508, so that one is OK. >>> There seem to be some unmapped IO changes between r248509 and r248706, >>> (e.g. r248510-r248512, r248514-r248522, r248550, r248568-r248569, >>> r248596) but I think it is more related to something closer to >>> userland? >>> >>> But the other commits between r248508 and r248706 look OK to me >>> (including r248534 (jilles, SOCK_CLOEXEC, SOCK_NONLBOCK, >>> MSG_CMSG_CLOEXEC)) >>> >>> >>> Are you able to continue bisecting those changes? >>> >>> Thanks for your help so far! >>> >> Checkpoint: r248509 boots fine (including init), but running e.g. python >> built under r247742 dumps core during startup. >> kdump output: ftp://rene-ladan.nl/pub/freebsd/python2.7.ktrace >> > Maybe it has to do with the fix applied to libsupc++ in r248624 to get > this program working: > > % cat testcpp.cc > #include > > using namespace std; > > int main(void) { > try { > throw "throwme"; > } > catch (const char* msg) { > cout << msg << endl; > } > > return 0; > } > > With an older libsupc++ , one gets: > % /home/pi/testcpp > /usr/lib/libsupc++.so.1: Undefined symbol "_Unwind_RaiseException" > % > I just upgraded to r248706 again and it boots fine. The difference with the earlier upgrade is that I now cross-install kernel and world so that the architecture is compatible with the cross-build architecture. I used a native 'make installkernel' / 'make installworld' upgrade earlier which required some ad-hoc install hacks. testcpp runs fine again with the libsupc++ fix: % /home/pi/testcpp throwme % python still dumps core, maybe it needs to be forcibly rebuilt? I'll upgrade to todays CURRENT to see how that behaves. René