[#6660] Ruby on Neko ? — Nicolas Cannasse <ncannasse@...>

Hi folks,

14 messages 2005/11/19

[#6672] testing for hardlink with "test(?-, ...)" flawed on Windows — noreply@...

Bugs item #2858, was opened at 2005-11-20 16:35

13 messages 2005/11/20

[#6684] semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...>

Hi all,

81 messages 2005/11/21
[#6685] Re: semenatics of if/unless/while statement modifiers — Mauricio Fern疣dez <mfp@...> 2005/11/22

On Tue, Nov 22, 2005 at 08:22:59AM +0900, Stefan Kaes wrote:

[#6686] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

Mauricio Fern疣dez wrote:

[#6687] Re: semenatics of if/unless/while statement modifiers — Eric Hodel <drbrain@...7.net> 2005/11/22

On Nov 21, 2005, at 4:37 PM, Stefan Kaes wrote:

[#6689] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

Eric Hodel wrote:

[#6693] Re: semenatics of if/unless/while statement modifiers — Yukihiro Matsumoto <matz@...> 2005/11/22

Hi,

[#6695] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

Yukihiro Matsumoto wrote:

[#6718] Re: semenatics of if/unless/while statement modifiers — mathew <meta@...> 2005/11/22

[#6722] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

mathew wrote:

[#6707] Re: semenatics of if/unless/while statement modifiers — "David A. Black" <dblack@...> 2005/11/22

Hi --

[#6708] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

David A. Black wrote:

[#6714] Re: semenatics of if/unless/while statement modifiers — "David A. Black" <dblack@...> 2005/11/22

Hi --

[#6717] Re: semenatics of if/unless/while statement modifiers — Stefan Kaes <skaes@...> 2005/11/22

David A. Black wrote:

[#6798] ruby 1.8.4 preview2 — Yukihiro Matsumoto <matz@...>

Hi,

37 messages 2005/11/30

Re: Stack trace consumes information. patch...

From: Christian Neukirchen <chneukirchen@...>
Date: 2005-11-05 11:23:23 UTC
List: ruby-core #6576
Hugh Sasse <hgs@dmu.ac.uk> writes:

> On Sat, 5 Nov 2005, Eric Hodel wrote:
>
>> On Nov 4, 2005, at 11:45 AM, Hugh Sasse wrote:
>> 
>> > In those missing 9 levels is the information I need about where my
>> > call to the library was.  I.e. that would tell me which table I was
>> > accessing at the time.
>> 
>> Or you could just rescue the exception and print out the backtrace.
>> 
>> begin
>>   generate_big_stacktrace_and_raise
>> rescue
>>   puts $!.backtrace.join("\n")
>> end
>
> I'd missed that, thanks.  But I'd still like more of it in the
> default case:  5 levels down from the outside isn't very deep to
> start trimming.

Maybe always show a full backtrace with -d or -w given?

>         Hugh
-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org

In This Thread

Prev Next