[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35251] Re: [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order

From: KOSAKI Motohiro <kosaki.motohiro@...>
Date: 2011-02-15 13:31:19 UTC
List: ruby-core #35251
> btw, C's atexit() has different behavior.
>
> (snip)
>
> % gcc at_exit.c; ./a.out
> outer3
> outer2_begin
> outer2_end
> inner2
> outer1_begin
> outer1_end
> inner1
> outer0

Python has the same behavior with C.

test_atexit.py
-----------------------------------------------------------------
import atexit

def func0():
        print "outer0"

def func1_internal():
        print "inner1"

def func1():
        print "outer1_begin"
        atexit.register(func1_internal);
        print "outer1_end"

def func2_internal():
        print "inner2"

def func2():
        print "outer2_begin"
        atexit.register(func2_internal);
        print "outer2_end"

def func3():
        print "outer3"

atexit.register(func0);
atexit.register(func1);
atexit.register(func2);
atexit.register(func3);
-----------------------------------------------------------------

In This Thread