Bug #2646

1.9.2dev segv when compiling with clang 1.1/trunk

Added by Ollivier Robert almost 6 years ago. Updated over 4 years ago.

Status:Third Party's Issue
ruby -v:ruby 1.9.2dev (2010-01-25) [x86_64-darwin10.2.0] Backport:


As I've been doing for several months/years, I'm compiling regular snapshots of the clang compiler and use it to compile ruby/trunk.
I have clang@94309 and ruby 1.9.2dev@26404 on OS X 10.6.2. For several revisions of ruby I get this when running miniruby during the build process:

clang -O -m64 -g -pipe -I. -I.ext/include/x86_64-darwin10.2.0 -I../include -I.. -DRUBY_EXPORT -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -o newline.o -c newline.c
clang -O -m64 -g -pipe -L. -m64 -g -L/usr/local/lib -Wl,-u,objc_msgSend main.o dmydln.o dmyencoding.o miniprelude.o array.o bignum.o class.o compar.o complex.o dir.o enum.o enumerator.o error.o eval.o load.o proc.o file.o gc.o hash.o inits.o io.o marshal.o math.o node.o numeric.o object.o pack.o parse.o process.o random.o range.o rational.o re.o regcomp.o regenc.o regerror.o regexec.o regparse.o regsyntax.o ruby.o safe.o signal.o sprintf.o st.o strftime.o string.o struct.o time.o transcode.o util.o variable.o version.o compile.o debug.o iseq.o vm.o vmdump.o thread.o cont.o ascii.o us_ascii.o unicode.o utf_8.o newline.o dmyext.o -lpthread -ldl -lobjc -o miniruby
internal:prelude:4: [BUG] Segmentation fault
ruby 1.9.2dev (2010-01-25) [x86_64-darwin10.2.0]

-- control frame ----------
c:0003 p:0002 s:0006 b:0006 l:000005 d:000005 TOP internal:prelude:4
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:0000 s:0002 b:0002 l:000238 d:000238 TOP

internal:prelude:4:in `'

-- C level backtrace information -------------------------------------------

You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

make: *** [.rbconfig.time] Abort trap

Any idea/test I could ru to see whether it is a clang-related issue or a ruby one?


#1 Updated by Roger Pack almost 6 years ago


Any idea/test I could ru to see whether it is a clang-related issue or a ruby one?

I'm not familiar with "clang", but if it has the equivalent of gdb, you could try running it in that, and/or valgrind.

#2 Updated by Yui NARUSE almost 6 years ago

Hmm, it seems your clang's bug.
I can compile with clang 1.1 with x86_64 FreeBSD.

Anyway, it seems crash of miniruby.
Can you try following?
gdb ./miniruby -e'1'

#3 Updated by _ wanabe over 5 years ago

  • Target version changed from 1.9.2 to 2.0.0



#4 Updated by Yui NARUSE over 5 years ago

  • Status changed from Open to Third Party's Issue



Also available in: Atom PDF