murphys@cod.NOSC.MIL (Steven P. Murphy) (02/25/89)
First off, Thanks to all those who replied with suggestions.
The segguestion I used was setting a trace point in CodeView and letting
it find the bad code. Like a number of people pointed out the NULL area
is at offset 0 within the data segment. But what caught me for awhile was
the fact that MS considers the first 64 bytes of the DS seg to be the null
pointer space (in QuickC 2.0). In CV after you have gotten to the first
line of code, type:
tpb ds:0 l64
This is a trace point of size byte starting at ds:0 and checking the next
64 bytes. I hope this helps someone else.
------------------------
S. P. Murphy
Internet: murphys@cod.nosc.mil UUCP: {ucbvax,hplabs}!sdcsvax!nosc!murphys