Date: Fri, 17 May 2013 11:05:14 +0200 From: Werner Thie <werner@thieprojects.ch> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Git crash on EABI system. Message-ID: <5195F2CA.2090103@thieprojects.ch> In-Reply-To: <2290084B-D302-4489-BB01-817497901E2B@freebsd.org> References: <A44A52E5-E878-45CD-B032-F111E5E244BA@freebsd.org> <51949698.80205@thieprojects.ch> <2290084B-D302-4489-BB01-817497901E2B@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/16/13 11:04 AM, Tim Kientzle wrote: > > On May 16, 2013, at 4:19 AM, Werner Thie wrote: > >>> Has anyone else seen this from git on a clang/EABI system? >>> >>> Assertion failed: (attr_stack->origin), function prepare_attr_stack, file attr.c, line 630. >>> >>> Program received signal SIGABRT, Aborted. >>> [Switching to Thread 20c03300 (LWP 100076/git)] >>> 0x204b842c in thr_kill () from /lib/libc.so.7 >>> (gdb) bt >>> #0 0x204b842c in thr_kill () from /lib/libc.so.7 >>> #1 0x2044157c in raise () from /lib/libthr.so.3 >>> #2 0x20598130 in abort () from /lib/libc.so.7 >>> #3 0x20574630 in __assert () from /lib/libc.so.7 >>> #4 0x00076b28 in ?? () >>> >>> I'm planning to do a debug build and see if I can track down any >>> more details. >> >> Hi Tim >> >> just built git out of curiosity after your post on the BBone >> >> FreeBSD beaglebone 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250144M: Sat May 4 14:18:20 CEST 2013 root@xtools:/usr/home/wthie/proj/crochet-freebsd/work/obj/arm.armv6/usr/local/src/sys/BEAGLEBONE-NOWITNESS arm >> >> git crashes exactly as advertised when cloning a project in >> >> Assertion failed: (attr_stack->origin), function prepare_attr_stack, file attr.c, line 630. > > Thanks for verifying that. Tim Maybe you or somebody else can shed some light onto how compiler-rt is used for the ARM platform, specifically why am I getting a missing symbol __clear_cache when building ctypes for Python. I tried several ways to preset WITH_ARM_EABI on make.conf but the def never shows up when compiling Python nor one of the other extension modules. I assume the def is generally set and the missing symbol is courtesy of some other error/omission. Thxs, Werner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5195F2CA.2090103>