Re: selective disabling of crash reports
Re: selective disabling of crash reports
- Subject: Re: selective disabling of crash reports
- From: Jean-Daniel Dupas <email@hidden>
- Date: Sun, 18 Jan 2009 17:17:00 +0100
It disables the crash windows, not the crash reporter.
The Crash Reporter will continue to generate Crash log and to slow
down the test.
Le 18 janv. 09 à 17:09, Jeff Johnson a écrit :
Iain,
Launch "/Developer/Applications/Utilities/CrashReporterPrefs.app"
and select Server.
-Jeff
On Jan 18, 2009, at 7:07 AM, IainS wrote:
Hello,
Whilst crash reporter is a very useful and wonderful item - there
are certain circumstances in which it can get in the way.
In particular, if one is regression-testing on a multi-core machine
(i.e. you *expect* a lot of crashes) then there is a problem where
the crash report mechanism gives out a "too many crashes" log
message and seems to stall for a while. This also sometimes gives
false results on the testing (i.e. it seems that an executable has
failed by timing out).
I have read tn2123 and the crash report man page.
The latter seems to indicate that I can disable crash reporting
"for everything" involving a re-boot (by setting appropriate flags
in launchd controls).
I'd much prefer to disable the crash reports only for the sessions
that are unit testing (since I find that crash reports are
generally helpful).
Also a re-boot per change is not terribly attractive...
Does anyone know of a more selective way of dealing with this?
tia,
Iain
_______________________________________________
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
_______________________________________________
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