Creating a bootstrap program and using URL schemes may be an option for some people, and, of course, it should be taken into account, but this does not meet my requirements.
What I ended up with was launching the application using the debugger using the fruit utility. I reassembled the fruit tray to include the following preparation commands (in the GDB_PREP_CMDS definition):
handle all noprint pass nostop continue
The descriptor will transmit the signal to the program, so that the signal handler (accident handler in this case) will process the signal. The sequel was something I needed for the application to really start after the debugger started.
There is one unfortunate drawback in this, unfortunately, I do not know a workaround. The GDB version for ARM7 does not have the command 'set dont_handle_bad_access', as does the darwin version. For some reason, passing EXC_BAD_ACCESS signals to the program does not work, and the application freezes. This is important because it is the signal for most failures. But since it stands now, this is the best I can do, and at least its handling of exceptions thrown.
Bluevoid
source share