From: Ralph Shnelvar Date: 2010-07-29T06:09:07+09:00 Subject: Re: rubyw, RuntimeError, capturing the stack, FXRuby ------------9A4BA22594521D Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Joseph, This does not give the call stack with file names and line numbers of the exception. Thanks. Ralph Wednesday, July 28, 2010, 2:58:20 PM, you wrote: JES> begin JES> puts 1/0 JES> rescue Exception, NameError => e JES> print "this is an error [#{e}]" JES> print $!.inspect #Ruby places a reference to the associated Exception JES> object into the global variable $! JES> end JES> output: this is an error [divided by 0]# >> From: Ralph Shnelvar >> Organization: Ralph Shnelvar >> Reply-To: >> Date: Thu, 29 Jul 2010 05:44:36 +0900 >> To: ruby-talk ML >> Subject: rubyw, RuntimeError, capturing the stack, FXRuby >> Let's say I'm running rubyw and a RunTimeError is raised ... >> and I'm using FXRuby (which is tangential to this question) ... >> and I want to put up a errorbox ... >> But I want to capture the error message that would normally go to stdout, i.e. >> the call stack ... >> How would I capture the call stack to a string in a raised exception? >> - - - >> begin >> raise RuntimeError, "Something bad happened" >> rescue >> # What do I do here? >> end >> - - - -- Best regards, Ralph mailto:ralphs@dos32.com ------------9A4BA22594521D--