Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com
From: @home.com
Newsgroups: scee.yaroze.programming.codewarrior
Subject: Re: Debugger problem
Date: Sat, 13 Jun 1998 15:47:40 -0700
Organization: SCEA News Server
Lines: 20
Message-ID: <3583018C.5A7F@home.com>
References: <6lemid$1293@chuka.playstation.co.uk> <357AE25F.83EEAC60@compuserve.com> <6lhivj$1294@chuka.playstation.co.uk>
Reply-To: @home.com
NNTP-Posting-Host: cs1000396-a.gvob1.bc.wave.home.com
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01-C-SYMPA (Macintosh; I; PPC)

I don't work for Metrowerks, but I thought I'd point out a couple of
things -

Setting your variables "volatile" removes any hope of your code being
optimized. You'll get MAJOR slow downs, in other words, and all the guys
using gcc will start saying nyah-nyah-nyah to you.

Check your compile settings instead. If you are building with
instruction scheduling or many other optimizations turned on, the
compiler doesn't give the symbol file any clues as to where a value
might be held at any point. Microsoft Visual C++ for Intel does this too
- it's not just Metrowerks.

If you set up a project using the recent project stationery, you'll
actually get two targets you can build - a debug version, and a release
version. The debug version will have all the switches turned off so you
can see your variables.

I hope this helps.
nick