[Mono-dev] [PATCH] don't write stack trace on stackoverflow

Kornél Pál kornelpal at hotmail.com
Sun Dec 25 05:57:53 EST 2005


I don't see any reason to hide the stack trace of StackOverflowException.
Stack trace helps tracking exceptions. If you want to hide automatic stack
traces printed by the runtime you should use try-catch blocks. Unless it has
advantages over printing the stack trace we should not hide it just to copy
MS.NET behavior.

What's the point of not to write stack trace on stack overflow?


----- Original Message -----
From: "Eyal Alaluf" <eyala at mainsoft.com>
To: "Jb Evain" <mono at evain.net>
Cc: "mono-devel-list" <mono-devel-list at lists.ximian.com>
Sent: Sunday, December 25, 2005 10:19 AM
Subject: Re: [Mono-dev] [PATCH] don't write stack trace on stackoverflow

> Maybe a limited stack - say the last 50 frames, would be better? It
> defintely
> hard to understand a stack overflow without at least part of the stack.
> Eyal.
> On Fri, 23 Dec 2005, Jb Evain wrote:
>> Date: Fri, 23 Dec 2005 23:11:20 +0100
>> From: Jb Evain <mono at evain.net>
>> To: mono-devel-list <mono-devel-list at lists.ximian.com>
>> Subject: [Mono-dev] [PATCH] don't write stack trace on stackoverflow
>> Hi,
>> This small patch prevents the stack trace from being printed when a
>> stackoverflow happens.
>> Ok to commit ?
>> Jb


> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list