[Yarv-devel] segfault on mingw

[gabriele renzi]

Hi, 
it seem that a strange bug appeared in latest
revisions:

c:/ruby/bin/ruby19 -I. ./test/runner.rb
Loaded suite test
Started
.....*eval*:11: warning: already initialized constant
C
*eval*:11: warning: already initialized constant C
*eval*:11: warning: already initialized constant C
<*YARV eval*>:14: warning: already initialized
constant C
<*YARV eval*>:14: warning: already initialized
constant C
<*YARV eval*>:14: warning: already initialized
constant C
...............E................................................................
.....
Finished in 1.803 seconds.

c:/ruby/lib/ruby/1.9/test/unit/util/backtracefilter.rb:16:
[BUG] Segmentation fa
ult
ruby 1.9.0 (2005-01-03) [i386-mingw32]


This application has requested the Runtime to
terminate it in an unusual way.
Please contact the application's support team for more
information.
make: *** [test-all] Error 3
  

Interesting things:
the bug does not appear if "ruby -I. ./test/runner.rb"
is run from gdb, or from cmd.exe. It only appears when
the command is run from make, or from sh.exe, so I
think it relates to some environment stuff reflecting
on ruby (i.e. different stack limit). 

I don't have a clue on how to get a core file on
windows sorry :/

environment:
win xp pro SP2
athlon 2000+
sh --version
GNU bash, version 2.04.0(1)-release (i686-pc-msys)

gcc --version
gcc.exe (GCC) 3.4.2 (mingw-special)

ruby19 -v
ruby 1.9.0 (2005-01-03) [i386-mingw32]

yarv rev:109

=====
icq #69488917


		
___________________________________ 
Nuovo Yahoo! Messenger: E' molto più divertente: Audibles, Avatar, Webcam, Giochi, Rubrica
 Scaricalo ora! 
http://it.messenger.yahoo.it