Or just a dud memory module?
Sent from my iPhone
___
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/Unsubsc
On 24-Mar-09, at 1:06 PM, David H. Silber wrote:
Where would I look for information on what happens where?
What does the crash log say?
(usually recorded in ~/Library/Logs/CrashReporter)
M.
__
Mark Ritchie
Cocoa and WebObjects Developer
Diamond Lake Consulting Inc.
Toronto, Ontario, Canada
There are a number of API calls that may create a second thread for their
own background processing.
Most likely, you have corrupted memory somehow in your code on the main
thread, and it's (mostly) just a distraction that it eventually causes a
crash in thread 2. So standard memory debu
On Tue, Mar 24, 2009 at 1:06 PM, David H. Silber wrote:
> Where would I look for information on what happens where?
The crash logs? They're necessary for you (and the list) to
understand what "thread 2" even is, much less have any idea how/why it
crashed.
Incidentally, there are a number of
On Mar 24, 2009, at 10:06 AM, David H. Silber wrote:
The crash happens in thread 2. I haven't done anything to make the
application multithreaded, so I'm not sure what is supposed to be
happening in the various threads. Where would I look for
information on
what happens where?
I'm using tim
Hi folks,
I have an application that crashes under unknown circumstances after
it has been running (mostly hidden and ignored) for several days. This
most recent time it crashed when I woke the computer from sleep, but I
had done that several times since starting the application.
The crash happe
