Luis Lavena wrote: > Independent of being mingw or mingw-w64 provided version of GCC, 4.6.x seems to segfault too. > ... In fact, i had sigsegv in mingw-w64 too. the problem came from msvcrt!longjmp dereferences ebp+8 which maybe inval...jojelino (jojelino _)
i had same issue before although it maybe not same one. The location of error triggered was msvcrt!_abnormal_termination. From gcc 4.6, ABI has changed so %esp can be invalid memory reference. so msvcrt!longjmp sigsegvs in this case. ...jojelino (jojelino _)
also i ran './ruby.exe -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext -- "./test/runner.rb"' here is the result. log files with some glitch(size>1000KB) have been pruned.jojelino (jojelino _)
hi i've modified dmalloc,pthreads-win32 to make it work win32. and dmalloc_t passed so far. and then, ruby is chosen to check memory leaks. for dmalloc to work with ruby, some part of ruby has been patched. after successful build of r...jojelino (jojelino _)
=begin >>The patch seems wrong: first is the way check the gcc version, and the condition also wrong. the definitive solution would be leaving only following line :#define DECL_SC_REG(type, r, reg) register type reg_##r > ... to be ho...jojelino (jojelino _)
=begin it occasionally crashes, but i dun know where to start. it occured when freelist dereferences invalid freelist->as.free.next address. because the process accidentally terminated during collecting stack dump, you 'll need to w...jojelino (jojelino _)
=begin 1> at least i can assert that the stuff '\\?\' is windows-specific stuff that we don't like to be encountered. and i could see that cygwin do workaround by checking whether '\\?\ is present and ignore it. i'm happy to being said...jojelino (jojelino _)
jojelino (jojelino _)07:50 PM Ruby Bug #5375: [mingw32] segfault on WinXP SP3 with 1.9.3dev@33347