users unduly.
Paul Sanders.
http://www.alpinesoft.co.uk
- Original Message -
From: "Paul Sanders"
To:
Sent: Wednesday, January 27, 2010 7:01 PM
Subject: Re: Uncaught exceptions not terminating my app
Here's the list of exceptions I silently ignore
On Sun, Feb 7, 2010 at 5:43 PM, Graham Cox wrote:
>
> On 08/02/2010, at 4:23 AM, Paul Sanders wrote:
>
>> do they really have 7 1/2 million bugs outstanding!?
>
>
> No - this is the total number of reports ever submitted, assuming the
> numbering started at 1, which is unlikely (maybe started at
On 08/02/2010, at 4:23 AM, Paul Sanders wrote:
> do they really have 7 1/2 million bugs outstanding!?
No - this is the total number of reports ever submitted, assuming the numbering
started at 1, which is unlikely (maybe started at 100). Many will be dupes,
not bugs, or fixed.
--Graham
NSSetUncaughtExceptionHandler instead.
--
- Original Message -
From: "Roland King"
To: "Paul Sanders"
Cc:
Sent: Sunday, February 07, 2010 3:28 PM
Subject: Re: Uncaught exceptions not terminating my app
I've been following this, it's very interesting, not a problem I've had but
worth knowing about. If you've isolated this issue to this degree it might be
worth filing a bug report about it.
On 07-Feb-2010, at 11:14 PM, Paul Sanders wrote:
> If anyone was following / interested in this, I made
If anyone was following / interested in this, I made one further discovery.
NSExceptionHandler delegates are not called if an exception is raised in a
subthread. Instead, the app just silently terminates. Worse, on Snow Leopard
Crash Reporter fails to kick in, so you don't even get a crash rep
7:38 PM
Subject: Re: Uncaught exceptions not terminating my app
On 28 Jan 2010, at 18:55, Jens Alfke wrote:
>>
>
> There are various places in the frameworks where exceptions
> get caught and (mostly) ignored. Some of these are where
> Carbon code (like the menu or open/save fi
On 28 Jan 2010, at 18:55, Jens Alfke wrote:
>>
>
> There are various places in the frameworks where exceptions get caught and
> (mostly) ignored. Some of these are where Carbon code (like the menu or
> open/save file panel implementation) calls into Cocoa, since throwing an
> exception out th
uot;
To: "Paul Sanders"
Cc: "Ken Thomases" ;
Sent: Thursday, January 28, 2010 6:55 PM
Subject: Re: Uncaught exceptions not terminating my app
There are various places in the frameworks where exceptions get
caught
and (mostly) ignored. Some of these are where Carbon code (lik
On Jan 28, 2010, at 9:53 AM, Paul Sanders wrote:
No more dangerous then doing a random longjmp back to the event
loop, which is what happens if you let the exception unwind. As I
say, the frameworks do not appear to use exception handling
internally, other than to get back to the event lo
- Original Message -
From: "Jens Alfke"
To: "Paul Sanders"
Cc: "Ken Thomases" ;
Sent: Thursday, January 28, 2010 4:34 PM
Subject: Re: Uncaught exceptions not terminating my app
On Jan 28, 2010, at 12:10 AM, Paul Sanders wrote:
>> If you don'
On Jan 28, 2010, at 12:10 AM, Paul Sanders wrote:
> If you don't crash the app, you don't get the stack trace. No
> stack trace = no clue about what went wrong.
That's why I said the error alert should include the same "Report" button as
the crash report would.
> And we do offer to
> save
ow Leopard,
maybe that is good enough...
Paul Sanders.
- Original Message -
From: "Scott Ribe"
To: "Paul Sanders"
Cc:
Sent: Thursday, January 28, 2010 2:23 PM
Subject: Re: Uncaught exceptions not terminating my app
> If you don't crash the app, you don&#x
> If you don't crash the app, you don't get the stack trace. No
> stack trace = no clue about what went wrong.
Just yesterday I was working on some new code, which threw an exception, and
the logged message included the stack trace. Never seen that before, so I
assume it's new in Snow Leopard. At
--- Original Message -
From: "Jens Alfke"
To: "Paul Sanders"
Cc: "Ken Thomases" ;
Sent: Wednesday, January 27, 2010 7:27 PM
Subject: Re: Uncaught exceptions not terminating my app
On Jan 27, 2010, at 11:01 AM, Paul Sanders wrote:
> My basic tenet is that I w
On 1/27/10 11:27 AM, Jens Alfke said:
>> My basic tenet is that I want to catch unexpected exceptions and
>> terminate my app in a way that produces a crash report containing a
>> proper stack trace.
>
>As a developer I understand your desire; but as a user, I would rather
>have your app pop up an
On Jan 27, 2010, at 11:01 AM, Paul Sanders wrote:
My basic tenet is that I want to catch unexpected exceptions and
terminate my app in a way that produces a crash report containing a
proper stack trace.
As a developer I understand your desire; but as a user, I would rather
have your app
PS: I just noticed you work for CodeWeavers, Ken. Salutations.
- Original Message -----
From: "Ken Thomases"
To: "Paul Sanders"
Sent: Thursday, January 21, 2010 5:14 PM
Subject: Re: Uncaught exceptions not terminating my app
Your exception handler should b
On Jan 20, 2010, at 1:27 PM, Paul Sanders wrote:
> I am experiencing a strange problem with the handling of uncaught exceptions
> which I'm hoping someone can shed some light on.
>
> This document:
>
> http://developer.apple.com/mac/library/DOCUMENTATION/Cocoa/Conceptual/Exceptions/Tasks/Contro
Greetings all,
I am experiencing a strange problem with the handling of uncaught exceptions
which I'm hoping someone can shed some light on.
This document:
http://developer.apple.com/mac/library/DOCUMENTATION/Cocoa/Conceptual/Exceptions/Tasks/ControllingAppResponse.html#//apple_ref/doc/uid/2000
20 matches
Mail list logo
