Re: [PATCH] fixed SIG_SEGV in check_stack() in eval.c

OK, here it is (slightly modified, but the Ruby parts
are left intact.  Yahoo mail is gonna wrap these
lines, so I've put blank lines between each stack
frame.

$ pstack core

core 'core' of 7541:

 ff11efd0 _lwp_kill (6, 0, 0, ffffffff, 12ab7b0,
1167fcc) + 8

 ff0b595c abort    (ff13c000, 2d, ff143a4c, ff13fca0,
1167fe8, 1167c00) + 100

 00f0b674 rb_bug   (1165798, 1165400, 0, 0, 0, 0) +
104

 00ed52f0 sigsegv  (b, 0, ffbea090, 0, 0, 0) + 10

 ff1b4cc8 __sighndlr (b, 0, ffbea090, ed52e0, 0, 0) +
c

 ff1afb00 call_user_handler (ff1c75a8, 1, ff1c78e0,
ffbea090, 0, b) + 254

 ff1afccc sigacthandler (ff1c75a8, 0, ffbea090,
ff1c6000, 0, b) + 64

 00e5e3d0 stack_check (11a5400, 0, 1d4e8600, 197fa458,
1, 0) + e8

 00e4cb0c rb_call0 (1d65fc8, 1d65fc8, 2829, 2829, 0,
0) + 108

 00e4dcec rb_call  (1d65f80, 1d65fc8, 2829, 0, 0, 1) +
320

 00e4e02c rb_funcall (1d65fc8, 2829, 0, 0, 1456508,
1332ad0) + 150
 -- first entry into Ruby

 00fbd008 Ruby__simulated_compare__test__Fv (1180c00,
12c19c7, 12c19c6, 0, 40a00831, 0) + 688
 -- my test function

 00fbc044 SCRIPT__simulated_compare__test__Fv
(ffbea7d8, ffbea7d8, 1332b18, 184c8f40, 1667cf0, 0) +
50
 -- my test function

 007ea63c <some_func> (ffbeb078, 197fa458, 19aa3ac, 9,
19af610, 0) + 30

 007ec0b0 <some_func> (ffbeb078, 197fa458, 19aa3ac,
18f58c6c, 1, 10000) + 160

 0091aa08 <some func> (19aa3ac, 197fa458, 19aa3ac,
197fa458, 1, 0) + 8c

 0091ad90 <some func> (100000, 100000, 2180000,
100000, 0, 0) + 174

 009219a8 <some func> (1456508, 2000000, 2180000, 0,
1, 0) + 204

 00924d10 <some func> (1456508, 12ef85c, f262b0,
11a6514, 1456508, 1332ad0) + 220

 009299dc <some func> (1456508, 11a6400, 10d0800,
ffbead58, 2, 2) + 6c

 008e484c <some func> (1456508, ffbeb5d4, ffbeac58,
ffbead58, 12abc08, 12abc08) + 11c

 008e4f6c <some func> (1456508, 0, 1, ffbead58,
ffbeb5d4, ffbeae58) + 534

 0075e5cc <some func> (1327028, ffbeb5d4, 0, 0, 0, 0)
+ 180

 00769bfc <some func> (1327028, ffbeb5d4, f1dc00,
578a2a91, 0, 0) + 338

 008540a4 <some func> (12f6010, ffbeb488, ffbeb450,
ffbeb448, ffbeb5d4, 0) + 114

 00850550 <some func> (12f6010, 12ef9a0, 12ef978,
12df010, 0, 0) + 3a14

 0073a000 <some func> (12ef850, 0, 0, ffbebe60,
10a0318, ffbebe60) + 4f8

 0072f228 <some func> (12ef850, ffbebe60, 0, 0, 0,
12ef850) + 4f9c

 0073eba0 <some func> (12ef850, 11a65bc, 109fae8, 0,
0, 0) + 29c

 007f0c44 <some func> (12ef850, 12ef850, 1, ffbee6c8,
10443b8, 10c7c00) + dfc

 001af438 main     (5, ffbee4a4, ffbee4bc, 12ab7b4, 0,
0) + 26a4

 001aba74 _start   (0, 0, 0, 0, 0, 0) + 5c


--- [e-mail] wrote:
> Hi,
> 
> At Sat, 22 May 2004 09:16:10 +0900,
> b g wrote in [ruby-core:02918]:
> > I can't provide a test case ;-( because I'm
> embedding
> > Ruby inside a commercial product.  The crash
> occurs
> > after the app has been running for ~20minutes,
> with
> > about 23 million calls on Ruby's rb_funcall()
> routine.
> >  (I'm calling a simple method I added to Object by
> > doing def method_name; ...; end;  That method
> simply
> > accesses a few $global variables [Floats], both
> > reading and writing them.)
> 
> Can't you show us the stack trace?
> 
> -- 
> Nobu Nakada
> 



	
		
__________________________________
Do you Yahoo!?
Yahoo! Domains Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer