OK. I discovered the culprit. It was a T2K/FMP TAF that had not been
converted to W5/MySQL.
Chris
>
> The lack of a log there means that the CrashReporter did not catch any of the
> error or core dump data around that app's crash. I've only seen one crash
> like this myself. And I'm sorry to say I don't know what the cause was.
>
> FYI ... in addition to the location below, CrashReporter logs may also exist
> in a similar location under each user's home directory.
>
> - Jeff
>
>
>> No log by that name. Is that a problem?
>>
>> Chris
>>
>>>
>>> Is there an entry for these crashes in
>>> /Library/Logs/CrashReporter/witangod.crash.log ?
>>>
>>> (Threadpoolsize is fine -- apparently there can be problems if you increase
>>> it.)
>>>
>>> - Jeff
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
