I'm using the CSet++ Tools Debug Memory Management Features (/Tm) to get
the memory leaks/overwrites out of my app.

Any tips on tracking down overwrites such as the following?

"An internal data structure starting at address 0x00662940 was
overwritten."

The Memory Leaks are actually quite easy to find, since it gives the
filename and line number where the leaked memory was allocated. :-)

Its these "internal data structure" overwrites that are hard to find.

Any suggestions are welcome.

Phil Crown
pcrown{at}airmail.net
http://web2.airmail.net/pcrown/

--- Blue Wave/OS2 v2.30