Re: a missing feature in VC debugger
- From: Ian Semmel <isemmelNOJUNK@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Jul 2006 04:21:11 +1000
All this discussion has been centering around the error of p == null, when there is, of course, a zillion values that p could have which will cause the program to crash or fail, but only one value to make it work as designed.
Tony Young wrote:
Hi,.
From time to time, when debugging why applications crash, we found out the cause is something similar to the following situation where p is actually a null pointer at run time:
p->func();
or
n = p->nData;
Finding this type of bugs are sometimes time consuming because applications may crash at a much later location. I don't know why VC6++ doesn't automatically detect such a situation and issue a warning. Does VC2005 has such feature? This should be a handy and easy-to-implement feature for the VC debugger. Does any other debugger support this type of feature? Your advice is appreciated.
JD
- Follow-Ups:
- Re: a missing feature in VC debugger
- From: Tom Serface
- Re: a missing feature in VC debugger
- References:
- a missing feature in VC debugger
- From: Tony Young
- a missing feature in VC debugger
- Prev by Date: Re: transparency in dlg
- Next by Date: Re: Is MSDN wrong? or I made a mistake? about static member function
- Previous by thread: Re: a missing feature in VC debugger
- Next by thread: Re: a missing feature in VC debugger
- Index(es):
Relevant Pages
|
