# Segmentation fault: Ruby 1.8.5 Under VC++ express 2005

**URL:** <https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035>\
**Category:** Ruby\
**Created:** [February 9, 2007, 12:56pm UTC](https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035 "2007-02-09T12:56:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zmzmzm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/ac8455/32.png) [@zmzmzm](https://www.ruby-forum.com/u/zmzmzm)\
**Post date:** [February 9, 2007, 12:56pm UTC](https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035/1 "2007-02-09T12:56:26Z")

</div>

Hi,  
Have anybody tried to compile the 1.8.5 code with VC++ express 2005  
SP1 and Windows platform SDK 2003 R2? I have pass the compile. And  
when it run miniruby, coredump happens.  
----------------\>8-----------------------------------------------  
miniruby ./win32/mkexports.rb:9: [BUG] Segmentation fault  
ruby 1.8.5 (2007-01-31) [i386-mswin32\_80]  
----------------\>8----------------------------------------------

Both the stable version and the snapshot version have this problem. I  
am running the compilation on XP SP2.

Any help will be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![zmzmzm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/ac8455/32.png) [@zmzmzm](https://www.ruby-forum.com/u/zmzmzm)\
**Post date:** [February 9, 2007, 2:06pm UTC](https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035/2 "2007-02-09T14:06:33Z")

</div>

On 2/9/07, zm [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> am running the compilation on XP SP2.
> 
> Any help will be greatly appreciated!

I haven’t seen that, specifically, but I haven’t tried in over a year  
to compile with VS2005 (and have even less incentive to do so now that  
my primary machine is a Mac). I wouldn’t be surprised if something was  
linked in that used a different C runtime, which is the number one  
problem with even thinking about using VS2005.

I need to bug the folks at MS again and get them talking with people  
who actually care about this problem any longer.

(Curt, if you’re reading this, I’d say that MinGW is your best option  
at this point. I’ve heard nothing from them since RubyConf.)

-austin

---

<div class="post-metadata">

**Author:** ![zmzmzm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/ac8455/32.png) [@zmzmzm](https://www.ruby-forum.com/u/zmzmzm)\
**Post date:** [February 9, 2007, 6:46pm UTC](https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035/3 "2007-02-09T18:46:07Z")

</div>

On Feb 9, 7:53 pm, “zm” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> am running the compilation on XP SP2.
> 
> Any help will be greatly appreciated!

I have manage to “bypass” the error. The problem seems like whenever  
the miniruby trying to call a “popen” kind of things it will die.  
The 9th line of the mkexports is actually  
IO.foreach("|dumpbin -symbols " + objs.join(’ ')) do |l|

I generate a static file with the command line of dumpbin, and let  
IO.foreach read this file, then the compilation go through.

Again when do nmake test, it will fail at the execute quote `...`

Has anybody got the same issue here?

---

<div class="post-metadata">

**Author:** ![zmzmzm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/ac8455/32.png) [@zmzmzm](https://www.ruby-forum.com/u/zmzmzm)\
**Post date:** [February 9, 2007, 8:00pm UTC](https://www.ruby-forum.com/t/segmentation-fault-ruby-1-8-5-under-vc-express-2005/85035/4 "2007-02-09T20:00:18Z")

</div>

On 2/9/07, Austin Z. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > 
> 
> I need to bug the folks at MS again and get them talking with people  
> who actually care about this problem any longer.
> 
> (Curt, if you’re reading this, I’d say that MinGW is your best option  
> at this point. I’ve heard nothing from them since RubyConf.)

Yeah… I’m here. I was planning to go MinGW less something happenned  
along  
the way that presented a better option.

Curt
