[#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: ruby packer prototype: core dumps ( design review request )

From: "Adam Bozanich" <adam.boz@...>
Date: 2007-05-07 03:34:07 UTC
List: ruby-core #11105
On 5/3/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
>
> Hi,
>
> At Thu, 3 May 2007 15:30:14 +0900,
> Adam Bozanich wrote in [ruby-core:11079]:
> > Stepping through the debugger, the crash fails in rb_rescue2() in the
> > JUMP_TAG() macro when prot_tag is dereferenced ( it is null ).
>
> rb_rescue2() reraises the caught exception if it isn't
> handled.  You may want to use rb_protect() instead.
>
>
Thank you, that did the trick.  I had overlooked the fact that rb_rescue()
calls rb_rescue2() with rb_eStandardError rather than rb_eException.
Strangely enough, when I use rb_protect(), there aren't any exceptions being
thrown as far as I can tell.  go figure.

Thanks again,
-Adam

In This Thread

Prev Next