Strange debugger behavior

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bint - 27 Sep 2005 02:26 GMT

Hello,

I am trying to debug my program, and when it's crashing, instead of
stopping at the point in the source where it crashed, it does something I
haven't seen before.

A second window opens up as it crashes, and it's a second debug window with
all of the play,stop, and step controls. It says it's for a different
thread than my main window's thread. The code in the new window is
illegible, machine stuff from dylib or something.

If I close the new thread window, I have to kill the whole process.

How can I tell where my program is crashing? I am not aware of starting any
threads separate from my progam, and I'm barely aware of what that even
means, having multiple threads...

Thanks
Bint

Reply to this Message

Peter Paulus - 27 Sep 2005 08:26 GMT

Hello Bint,

Why don't you let your program run and crash freely. After it has
crashed you can inspect the CrashLog in the folder
'~/Library/Logs/CrashReporter'. The name of the file depends on your
application. In this file you can find what each tread is doing at the
time of the crash. You can also see what (dynamic libraries) were in use
and the state of processor registers.

Hope that helps in any way.

With kind regards,
Peter Paulus

> Hello,
>
[quoted text clipped - 15 lines]
> Thanks
> Bint

Reply to this Message

Bint - 27 Sep 2005 17:15 GMT

Thanks, but my crashlogs don't seem to have updated recently. It would be
the name of my program, right? Not CodeWarrior.

Well, the crashlog for my app was last modified on Sept. 10. That is weird.

Bint

On 9/27/05 2:26 AM, in article 4338f427$0$306$4d4ebb8e@news.nl.uu.net,

> Hello Bint,
>
[quoted text clipped - 29 lines]
>> Thanks
>> Bint

Reply to this Message

Mac Forum / Programming / CodeWarrior / September 2005

Strange debugger behavior