Turbo C++ 3.0 bugs

[mbbrutman-cctalk at brutman.com]

Quoting Jim Leonard <trixter at oldskool.org>:

> I hate to mention the obvious, but have you tried tracing through the code in
> a 
> debugger to see what is actually happening?  If the first call fails but the
> 
> second call works, that is (in my experience) something very easy to
> determine 
> the cause of in a debugger.


No debugger ..  while I'm a fan of debuggers (and I did a lot of work to
implement the one on the BlueGene supercomputer), adding the extra symbols
changes too much stuff.  And in particular, the debugger in this IDE is
attrocious. :-)  If I had the stand-alone Turbo Debugger I might try it.

What I really need is good listing and disassembly tools ... working with
straight debug sucks.