[#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

[ ruby-Bugs-11151 ] exception in at_exit --> 0 exit status

From: <noreply@...>
Date: 2007-05-26 23:19:53 UTC
List: ruby-core #11263
Bugs item #11151, was opened at 2007-05-27 01:19
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11151&group_id=426

Category: Core
Group: 1.8.6
Status: Open
Resolution: None
Priority: 3
Submitted By: Johan Holmberg (holmberg)
Assigned to: Nobody (None)
Summary: exception in at_exit --> 0 exit status

Initial Comment:
If an exception occurs in an at_exit block, the Ruby process still exits with a zero exit status. This seems wrong. Example code:

  $ ruby -e 'at_exit { raise "an error" }' ; echo $?
  -e:1: an error (RuntimeError)
          from -e:1
  0

All Ruby version I have tested work this way:

* 1.8.2
* 1.8.5
* 1.8.6
* subversion branch "ruby_1_8" from 2007-05-26
* subversion branch "ruby_1_8_6" from 2007-05-26
* subversion trunk from 2007-05-26

I tried all versions on Mac OS X, but I guess Ruby behaves this way on all platforms.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11151&group_id=426

In This Thread

Prev Next