Re: catching EXC_BAD_ACCESS?
Re: catching EXC_BAD_ACCESS?
- Subject: Re: catching EXC_BAD_ACCESS?
- From: "Jordan K. Hubbard" <email@hidden>
- Date: Mon, 21 Nov 2005 10:05:25 -0800
| As painful as it may be, can you reproduce this? It would DEFINITELY be worth a radar, if so.
As to some of the other comments in this thread (which has been very enlightening with respect to the issues that people are running into), if something is even non-obvious, please file a radar! These sorts of little fit-and-finish issues often fall through the cracks given our rapid development schedule, and even if you manage to find a work-around to some problem you run into, if the solution should have been more obvious then file a radar to that effect. Even in the worst-case scenario where the internal developer goes "dude, you should be doing it *this* way!" and sends the radar back as "not to be fixed", you've still made an impact since if the developer then gets 4 more bugs just like it, they're likely to start scratching their heads and going "Hmmm. OK, maybe there really is an issue here if people keep running into this. Maybe I can do something more clever than what I'm doing now."
- Jordan On Nov 21, 2005, at 9:06 AM, Brad Parker wrote: sa.sa_flags = SA_SIGINFO|SA_64REGSET;
heh. I added that to my FPE test program and the machine hung hard. I had to power cycle :-)
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden