Date: Fri, 31 May 2013 21:34:04 GMT From: Justin Hibbits <jhibbits@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: threads/179158: ruby19 segfaults during build on ppc64 Message-ID: <201305312134.r4VLY4Sl016500@oldred.FreeBSD.org> Resent-Message-ID: <201305312140.r4VLe03d052399@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 179158 >Category: threads >Synopsis: ruby19 segfaults during build on ppc64 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 31 21:40:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Justin Hibbits >Release: 10-CURRENT >Organization: >Environment: FreeBSD zhabar 10.0-CURRENT FreeBSD 10.0-CURRENT #9 r250992M: Sun May 26 02:03:28 PDT 2013 chmeee@zhabar:/usr/home/chmeee/world/usr/home/chmeee/freebsd/head/sys/ZHABAR powerpc >Description: Ruby 1.9 port segfaults during build when running miniruby. gdb points this to the thread management, a stack overflow. I don't think this is limited to just ruby, but may affect other programs as well. I categorize this under 'threads' so someone more familiar with threading might be able to find a quick solution. >How-To-Repeat: Build lang/ruby19 on powerpc64 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201305312134.r4VLY4Sl016500>