From: Nobuyoshi Nakada <nobu@...>
Date: 2008-02-15T10:57:57+09:00
Subject: Re: Timeout, WWW::Mechanize, core dump

Hi,

At Fri, 15 Feb 2008 07:10:37 +0900,
Daniel Berger wrote in [ruby-talk:291077]:
> Solaris 10
> Sun Studio Compiler 12
> ruby 1.8.6 (2007-09-24 patchlevel 111) [sparc-solaris2.10]
> mechanize 0.6.10
> rubygems 0.9.4
> 
> $CC => cc
> $CFLAGS => -g -dalign -fns -xbuiltin=%all -xlibmil -xtarget=ultra2e -
> xO5
> -xipo -xarch=sparc
> 
> I'm hitting a core dump with the following program. It works fine when
> I
> run it from the command line, but when run via cron it dumps core.

It seems similar to [ruby-dev:33611], and akr was suggesting
changing the following in gc.c from 0x80 to 0.

#if defined(sparc) || defined(__sparc__)
# define STACK_LENGTH  (rb_gc_stack_start - STACK_END + 0x80)

Could you try it?


Index: gc.c
===================================================================
--- gc.c	(revision 15479)
+++ gc.c	(working copy)
@@ -454,7 +454,5 @@ stack_end_address(VALUE **stack_end_p)
 # define STACK_END (stack_end)
 #endif
-#if defined(sparc) || defined(__sparc__)
-# define STACK_LENGTH  (rb_gc_stack_start - STACK_END + 0x80)
-#elif STACK_GROW_DIRECTION < 0
+#if STACK_GROW_DIRECTION < 0
 # define STACK_LENGTH  (rb_gc_stack_start - STACK_END)
 #elif STACK_GROW_DIRECTION > 0


-- 
Nobu Nakada