Tracking down Access Violations

[James Dunne]

Jarrett Billingsley wrote:
> "Jeremy" <Jeremy_member at pathlink.com> wrote in message 
> news:e4j2uv$7av$1 at digitaldaemon.com...
> 
> 
>>The "-g" option gives me "forward reference" errors so I cannot run it 
>>through a
>>debugger and get good results (correct?).
> 
> 
> That sounds like a bug.  You shouldn't get forward reference errors just by 
> turning on the "generate debug info" flag.  That's the best way to track 
> down the access violation - debug the program.  If you can get that 
> working...
> 
> (Of course, if you're like me, chances are this is caused by dereferencing a 
> null object reference.  Which could be checked by D before calling any 
> methods on objects, but Walter feels that access violations are _more_ than 
> enough to track down bugs.) 
> 

Hehe.. *poke poke*

I've run into this little snag before, when printf just doesn't cut it, 
and when AVs are just about as useless as JPEGs to Helen Keller...

-- 
Regards,
James Dunne