[#11073] segfault printing instruction sequence for iterator — <noreply@...>

Bugs item #10527, was opened at 2007-05-02 14:42

14 messages 2007/05/02
[#11142] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Nobuyoshi Nakada <nobu@...> 2007/05/10

Hi,

[#11188] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Paul Brannan <pbrannan@...> 2007/05/16

On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:

[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>

Hi all.

17 messages 2007/05/25

Re: Segmentation Fault in GC

From: Paul Brannan <pbrannan@...>
Date: 2007-05-22 15:33:34 UTC
List: ruby-core #11224
The first thing that looks fishy is that the line numbers in your stack
trace don't correspond to the right function in gc.c for ruby version
1.6.8.  For example:

#7  0x00028570 in mark_entry (key=1, value=718165568) at gc.c:461

Line 461 of gc.c reads:

458 static int
459 mark_hashentry(key, value)
460     VALUE key;
461     VALUE value;
462 {

So the line numbers seem to be off by 15 lines or so.  Are you running a
stock 1.6.8 or have you made changes?

Also, if you're going to be running 1.6, there two years worth of fixes
in the latest 1.6 branch that aren't present in 1.6.8 (there was never a
1.6.9 released).  In particular, there are some GC changes.  I don't
know if these changes would fix your problem or not.

I'm also suspect of building ruby with -Os.  Try building with -O0 and
see if that helps.

Paul


In This Thread

Prev Next