From: ts <decoux@...>
Date: 2006-05-17T17:27:48+09:00
Subject: Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS

>>>>> "n" == noreply  <noreply@rubyforge.org> writes:

n> The problem appears to stem from '/bin/bash' being a file, not a
n> directory -- Rails was doing a similar Dir.glob, referencing a
n> subdirectory of a plain file object, which was where I was seeing the
n> segfault in production.  On i386 it returns an empty array.  Building
n> with -O2 in the CFLAGS resolves the problem.  I understand if this
n> might�be a case of "so don't build with -O0" but I believe behavior
n> should be identical on both platforms, or at the very least not exhibit
n> a segfault on x86_64. 

 Well not really a problem with -O0 (i.e. it can possible to have a version
 which crash with -O2), but rather an alignment problem.

 This is the call rb_protect(rb_sys_warning()) which give the crash because
 rb_sys_warning() is a variadic function.




Guy Decoux