Hi,
After publishing an update of my app, I have received quite a few
crash dumps with very weird stack traces that I cannot understand and
fix.
Namely, the exception message says that AXTitle, or AXWindow or
AXValue or AXDocument etc. is unsupported by NSWindow, NSOpenPanel,
NSApplication and
Oleg,
I think you are misinterpreting an exception being raised as a crash of your
application. The bt's below are not crashes; they are exceptions being raised
(and caught) by appkit's accessibility.
I understand that you have a problem with your app crashing -- do you have some
actual crash
Hi Corbin,
Thanks for your quick response. You are right, I should have been more
specific. This is not a crash in precise meaning. This is an
unhandled exception raised by appkit's accessibility and caught by my
crash reporter facility that prints the stack trace and sends it to me
by e-mail.
Hi Oleg,
Unfortunately, the accessibility mechanism uses unexceptional exceptions
under the hood. These are a normal part of operation. They shouldn't be
unhandled though… are you sure you're reporting what you think you are?
-Ken
On Tue, Feb 2, 2010 at 6:41 PM, Oleg Krupnov
Thanks Ken,
I don't quite understand your response though. What do you mean by
unexceptional exceptions? How should I handle those exceptions, and
why should I, if I don't make any calls to accessibility frameworks at
all?
The report I have included in the first post is all I have so far.
On
Are you sure you are seeing unhandled exceptions, or simply NSExceptions
that are handled somewhere inside the Ax framework.
If it is the latter, then you'll need to allow NSExceptions from inside the Ax
framework to propagate to their handlers (also inside the Ax framework).
Note: Apple does
Oleg,
In addition to what Ken and Jesper said, you should be able to repro the
problem yourself. Just turn on accessibility in System Prefs, and start
something like Accessibility Inspector
(/Developer/Applications/Utilities/Accessability tools)
..corbin
On Feb 2, 2010, at 10:58 AM, Oleg
On Feb 2, 2010, at 11:09 AM, Jesper Storm Bache wrote:
Note: Apple does *not* guarantee that their implementation is
NSException free; you just should not see such exceptions being
thrown back to your code.
Agreed. In some cases exceptions are thrown internally but then
caught, so they
Fixed now, it worked like a charm! :)
Indeed, I was intercepting exceptions from the AX framework in my -
(BOOL)exceptionHandler:(NSExceptionHandler*)sender
shouldHandleException:(NSException*)exception mask:(unsigned int)mask
delegate method. This only occurs on Snow Leopard but not on Leopard.
My advice is: Don't do this in release builds. There is nothing that says that
Apple in the future will throw more exceptions inside their implementation (in
a different framework) - and you'll then have to patch your handler again.
Feel free to experiment with this kind of functionality in your
Good point, Jesper.
But in this case, how should I catch real unhandled exceptions and
send bug reports? What is the recommended best practice?
Thanks!
On Tue, Feb 2, 2010 at 10:22 PM, Jesper Storm Bache jsba...@adobe.com wrote:
My advice is: Don't do this in release builds. There is nothing
On Feb 2, 2010, at 12:41 PM, Oleg Krupnov wrote:
Good point, Jesper.
But in this case, how should I catch real unhandled exceptions and
send bug reports? What is the recommended best practice?
NSSetUncaughtExceptionHandler possibly. I haven't had to use it myself...
--corbin
Did you try:
NSException.h:
void NSSetUncaughtExceptionHandler(NSUncaughtExceptionHandler *);
Be aware that I don't have any experience with this API - my implementation has
top level exception handlers in relevant places, so I should never see an
uncaught exception.
Jesper
On Feb 2,
On Tue, Feb 2, 2010 at 2:28 PM, Jesper Storm Bache jsba...@adobe.com wrote:
Did you try:
NSException.h:
void NSSetUncaughtExceptionHandler(NSUncaughtExceptionHandler *);
I might be missing something here, but why would this be usable and
NSExceptionHandler not? NSExceptionHandler is
I doubt you are missing something you may be right that maybe
NSExceptionHandler can be used (with the right mask).
The only real input I have on this matter is that I consider it fragile to fail
if an Apple framework throws an exception internally.
You'll need to be able to detect exceptions
On Tue, Feb 2, 2010 at 3:41 PM, Oleg Krupnov oleg.krup...@gmail.com wrote:
Good point, Jesper.
But in this case, how should I catch real unhandled exceptions and
send bug reports? What is the recommended best practice?
As far as I know, you really can't. The problem is that what we would
16 matches
Mail list logo
