The only way I now is to prevent the exception to be caught by the
Crash Reporter. It can be done by disabling your task exception port.
#include <mach/mach.h>
task_set_exception_ports(mach_task_self(), EXC_MASK_BAD_ACCESS |
EXC_MASK_CRASH, MACH_PORT_NULL, NULL, NULL)
This is not something I would do in my software as it has some side
effects like preventing crash log generation, and it also affect the
bugger, but this is what your looking for I think.
-- Jean-Daniel
Le 22 sept. 2009 à 18:58, Mark Woods a écrit :
Easier said than done. It's QuickTime that's crashing.
I'm calling canInitWithFile first and checking for errors with
movieWithFile:error: but in certain instances it will still crash.
On Sep 22, 2009, at 5:53 PM, Kyle Sluder wrote:
On Tue, Sep 22, 2009 at 9:47 AM, Mark Woods
<mwoods...@googlemail.com> wrote:
The task checks the validity of certain files and in some cases,
the task
could definitely crash if the data is corrupt - that is the whole
purpose of
launching a separate task. This is not a problem as the
application notifies
the user if the task was not successful.
Perhaps instead of crashing, you should design this tool to return
nonzero if the file is invalid?
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
