This scenario seems to be happening more frequently: A bogus call of mine
(my problem) causes an Access Fault Exception. The Debugger shows me the
proper point in the code where I was accessing through a null pointer.
After pressing OK to the "Access Fault Exception" dialog, the Spinning Beach
Ball of Death shows up and the debugger no longer responds and has to be
"force quit".
I don't seem to recall this behavior on the MW 8.3 debugger.
Anyone else have this happen? Are all bets off for the life of the debugger
under these circumstances?
Stephen
Miro Jurisic - 14 May 2004 23:56 GMT
> This scenario seems to be happening more frequently: A bogus call of mine
> (my problem) causes an Access Fault Exception. The Debugger shows me the
> proper point in the code where I was accessing through a null pointer.
> After pressing OK to the "Access Fault Exception" dialog, the Spinning Beach
> Ball of Death shows up and the debugger no longer responds and has to be
> "force quit".
Do you see a console message telling you that gdb crashed? I have seen this kind
of thing when gdb freaks out -- the MW IDE does not cope with that at all, it
just croaks.
meeroh

Signature
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>
Stephen Greenfield - 15 May 2004 01:51 GMT
> Do you see a console message telling you that gdb crashed? I have seen this kind
> of thing when gdb freaks out -- the MW IDE does not cope with that at all, it
> just croaks.
No console message. But boy, the fans on my G5 go into overdrive!
Stephen
Stephen Greenfield - 15 May 2004 01:54 GMT
Hmmm -- now it's ANY time I break into the debugger, even for a
breakpoint...
I wonder if it's time to trash the debugger prefs? ....
Stephen
Miro Jurisic - 15 May 2004 02:06 GMT
> I wonder if it's time to trash the debugger prefs? ....
The standard dead chickens to wave at CodeWarrior are:
1. Throw out project data folder
2. Throw out MW preferences
3. Reinstall CW
4. Throw out LaunchServices cache files
in that order.
meeroh

Signature
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>
Stephen Greenfield - 15 May 2004 02:28 GMT
> 1. Throw out project data folder
> 2. Throw out MW preferences
> 3. Reinstall CW
> 4. Throw out LaunchServices cache files
Thanks, but it "mysteriously" started working again.
I'm fairly certain it was connected to MY project, because debugging worked
in the Appearance sample.
I had noticed that the usual debugging log window that appears had NOT been
appearing. I also trashed a streamed text file used for debugging -- I
*suspect* the file might have gotten HUGE! Not sure if I exceeded some
theoretical limit.
Incredibly, everything started working again.
Very strange, but better my fault than CodeWarrior's...
Thanks for your suggestions -- I'll keep them close by in case this sort of
thing happens again.
Stephen
MW Ron - 24 May 2004 22:43 GMT
>This scenario seems to be happening more frequently: A bogus call of mine
>(my problem) causes an Access Fault Exception. The Debugger shows me the
[quoted text clipped - 7 lines]
>Anyone else have this happen? Are all bets off for the life of the debugger
>under these circumstances?
We think we figured this out... It is our bug If you have Break On C++
Exception turned on, and anytime you set/clear a breakpoint, stop/start
a debugging session, the IDE tries to find one of the runtime library
source files. Since they are kept in a shielded folder, it wants to
search for it every time because it didn't find it previously.
The two options to get around this for now are to
either keep that setting off, or to add an access path to
{Compiler}MacOS X Support/Libraries/Runtime/(Source).

Signature
Metrowerks, one of the world¹s top 100 companies and influencers
in the software development industry. - SD Times May 2004
http://www.sdtimes.com/2004sdt100.htm
Metrowerks, maker of CodeWarrior
Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com