CW 8.3 debug problem

CW 8.3 debug problem

Post by Michael Ol » Sun, 06 Jul 2003 02:36:45



Hi,

I have a problem that is causing me to tear my hair out... Please someone
help...

Whenever I try to debug CW is saying something like "loading symbols", and
then nothing happens... CW simply freezes...

I'm working on and for OSX, creating a shared library (CFM). My runtime
settings of course has an app which is loading the library(I don't have
symbols for this app). I'm using the december 2002 tools from apple. I'm
using CW 8.3, and yes, I did build the libraries at the end of installation.
I'm running OSX 10.2.something.

The really crazy thing is that once, just once, a few months ago (yes, I've
been fighthing this problem for that long) I actually managed to debug. Just
once. Maybe I was just being nice to my mac that day...

Can anyone help?

Thanks,

Michael Olsen
XXXX@XXXXX.COM
 
 
 

CW 8.3 debug problem

Post by Michael Ol » Sun, 06 Jul 2003 22:56:34


and

I'm not sure how to tell, but I think yes.


I think it is. We need to do both CFM and MachO, and thought that starting
out with CFM would be the easiest.


Thanks for this info, it could well be what is causing my problems.


Greets,

Michael Olsen
XXXX@XXXXX.COM

 
 
 

CW 8.3 debug problem

Post by Sean McBri » Tue, 08 Jul 2003 04:48:36

In article < XXXX@XXXXX.COM >,



Am I able to debug Mach-O code running in CFM host just fine with CW 8.3
on 10.2.6. Vice verse maybe doesn't work, I don't know.
 
 
 

CW 8.3 debug problem

Post by Sean McBri » Tue, 08 Jul 2003 04:49:14

In article <3f06c9b1$0$5188$ XXXX@XXXXX.COM >,



You can try opening the app with PEFViewer; that won't work for Mach-O
apps.
 
 
 

CW 8.3 debug problem

Post by Andy Den » Sun, 13 Jul 2003 01:03:20

In article <3f05abe2$0$5154$ XXXX@XXXXX.COM >,



I think I know what's happening.

I've reported it as a bug.

It happens because you have told CW to run with the Symbols window in
front.

It keeps happening to you, and me!, by accident because the Q@#$!@#
Symbols window is always opened automatically when you run a debugging
session.

The solution is simple - make sure your project window is frontmost
before you run debugging sessions.

Hope this helps.