Making the Visual C++ 6.0 debugger not 'step in'
Posted
by Lars Bergstrom
on April 24th, 1999
Thankfully, the debugger gurus at Microsoft seem to have seen this problem, too. As a quick warning, this feature is not documented and was just 'mentioned' by Andy Pennell in his presentation entitled 'Power Debugging with Visual C++ 6.0', given at the Boston '99 Visual C++ Developer's Conference. It also only works in Visual C++ 6.0.
Open up your autoexp.dat file -- in Common\MSDev98\Bin -- and add a new section named ExecutionControl to the end of the file and then add lines of the form: function=NoStepInto
[ExecutionControl] CString::CString==NoStepInto CString:::operator==NoStepIntoThese three lines will cause the debugger not to step into the CString contructor or assignment operator. As is standard for any modifications to this file, you have to shut down and reload Visual C++ for this to take effect.
Date Last Updated: April 24, 1999

Comments
Attention: only one =, not two == before 'NoStepInto'
Posted by icebear on 01/30/2009 02:37pmCan't manage to set NoStepInto for std::vector template class
Posted by Legacy on 11/10/2000 12:00amOriginally posted by: Maarten van Casteren
I've tried to use the NoStepInto feature to prevent the debugger from stepping into the STL vector::operator[] function, which it does all the time if you use STL a lot.
I tried (one at the time, of course):
[ExecutionControl]
std::*=NoStepInto
std::vector::operator[]=NoStepInto
std::vector<*>::operator[]=NoStepInto
_STLD::vector<*>::operator[]=NoStepInto
_STLD::vector<Layer*,_STLD::allocator<Layer*> >::operator[]=NoStepInto
The first line being recommended by one of the other comments and the last line being what the call stack window displays. None of them works.
Would somebody know how to do this?
Thanks,
Maarten.
ReplyMore capabilities
Posted by Legacy on 08/29/2000 12:00amOriginally posted by: Dejan Seatovic
You can also use namespaces:
ATL::*=NoStepInto
std::*=NoStepInto
coomplete class
CString::*=NoStepInto
ReplyGreat! This was exactly what I've missed since years...
Posted by Legacy on 08/20/1999 12:00amOriginally posted by: Christoph Weber
... and of course was as usually nowhere documented by Microsoft...
ReplyTemplates?
Posted by Legacy on 05/03/1999 12:00amOriginally posted by: Nenad Caklovic
Does anybody know the format for template classes and template functions?
ReplyMore samples
Posted by Legacy on 04/27/1999 12:00amOriginally posted by: Simon Capewell
operator new=NoStepInto
; MFC
CObject::operator new=NoStepInto
CString::*=NoStepInto
CSize::*=NoStepInto
CPoint::*=NoStepInto
CRect::*=NoStepInto
ReplyCString:::operator==NoStepInto too many colons?
Posted by Legacy on 04/26/1999 12:00amOriginally posted by: Roger Onslow
I am assuming that
CString:::operator==NoStepInto
should really be
CString::operator==NoStepInto
Is this correct?
Roger
Reply