issue with libthr?
uzimac at da3m0n8t3r.com
Sun Jun 2 15:08:58 UTC 2013
On Sun, 2 Jun 2013 10:43:35 -0400, Mark Johnston <markj at freebsd.org> wrote:
>On Sat, Jun 01, 2013 at 12:54:14AM -0700, Waitman Gobble wrote:
>> I'm getting a ton of core dumps from Python and any software that uses
>> ie has USE_PYTHON_BUILD=yes in Makefile.
>> hundreds of msgs in dmesg:
>> pid 36637 (seamonkey), uid 1001: exited on signal 11 (core dumped)
>> pid 36986 (seamonkey), uid 1001: exited on signal 11 (core dumped)
>> pid 37054 (seamonkey), uid 1001: exited on signal 11 (core dumped)
>> pid 51780 (seamonkey), uid 1001: exited on signal 11 (core dumped)
>> pid 83350 (python2.7), uid 0: exited on signal 6 (core dumped)
>> from gdb it seems to me to be libthr related? I've noticed a couple updates
>> May.. wonder if it's related? I've only noticed this issue in the past
>> after a complete rebuild and updated.
>I've been running into this issue too - python 2.7 would crash when
>trying to rebuild databases/tdb and databases/py-sqlite3 with backtraces
>similar to what you have below. The python port itself hasn't changed in
>Reverting r250991 and rebuilding libc solves the issue for me:
Thanks for the info, I appreciate it. I had a heck of a time getting
database/py-sqlite3 to build as well.
My workaround to get it installed was to change the Makefile in WRKSRC
it was bombing out on the 'except AttributeError:' line.
So I just changed it to
since I didn't have the extensions option SQLITE, if you have that option then
just delete the whole block, nothing needed.
Of course the 'better' way is to find the source of the issue. :)
San Jose California USA
More information about the freebsd-current