NoStepInto not working in VS.NET ? - microsoft.public.vsnet.debugging

Message from discussion NoStepInto not working in VS.NET ?

Visual C# Team

View profile

More options Jan 30 2003, 5:55 pm

Newsgroups: microsoft.public.vsnet.debugging

From: "Visual C# Team" <csh...@microsoft.com>

Date: Thu, 30 Jan 2003 14:45:19 -0800

Local: Thurs, Jan 30 2003 5:45 pm

Subject: Re: NoStepInto not working in VS.NET ?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

There's a little more to the syntax than just what Andy describes. Here's
the comment from the source code:

/*
We read the inclusion/exclusion list from the registry at
PRODUCT_ROOT\NativeDE\StepOver

Each string value in that RegKey should have a decimal number for its name
and a
value in the following format:

RegExp=[No]StepInto

Where RegExp is a regular expression per the standard Visual Studio
regular
expression format, with the following additional escapes:

\cid: A C/C++ identifier
\funct: A C/C++ function name
\scope: A set of class/namespace specifiers for a function (i.e.,
ATL::CFoo::CBar::)
\anything: any string
\oper: a C/C++ operator

Due to an oversight, the items are evaluated in descending numeric
order instead of ascending order: the '20' rule will match before
'10'. The first matching rule is used. If no matching rule is
found, we step into. (i.e., there is an assumed entry of
MAX_INT \anything:=StepInto

examples:
---------

Don't step into members of CString[AWT], etc.:

1 \scope:CString.*\:\:.*=NoStepInto

Don't step into overloaded operators:

10 \scope:operator\oper:=NoStepInto

Don't step into ATL:: except for CComBSTR's non-operator members:

20 ATL\:\:CComBSTR::\funct:=StepInto
10 ATL\:\:.*=NoStepInfo

Don't step into templated things, unless they're merely templated
functions in a non-templated class:

20 \scope:\funct:=StepInto
10 .*[\<\>].*=NoStepInto
*/

-Jay

--
This posting is provided "AS IS" with no warranties, and confers no rights
"Visual C# Team" <csh...@microsoft.com> wrote in message
news:e8Q1MBNwCHA.2532@TK2MSFTNGP10...

> The syntax is based on normal VS regular expressions, as used in the Find
> dialog. The strings below look overly complicated because they are the
> contents of a REG file, and it needs extra escapes over and above the
regex
> escapes.

> The regex string .*CString.* means zero or more of any char, CString, then
> zero or more of any char, i.e. any function name with CString anywhere in
> it.

> The ATL regex string is ATL\:\:.* - the colons have to be escaped for
regex
> reasons. The double escaping is required as this example came from a REG
> file. This string means ATL, then two colons, then zero or more of any
char.

> Remember this feature is not officially documented or supported.

> Andy
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights
> "Michal Bacik" <mic...@lonelycatgames.com> wrote in message
> news:#gxFF6UvCHA.2304@TK2MSFTNGP10...
> > Thanks,
> > could you describe the syntax please, or point to some more information?
I
> > discovered I have to create string keys with arbitrary names, but the
> syntax
> > has changed since MSVC 6.
> > What does those dots in front and back of ".*CString.*" mean? And what
> about
> > the asterisks? Also you could post more examples with description of
what
> > they filter out.

> > Thanks a lot.
> > - Michal

> > "Bill Boris [MSFT]" <bbo...@online.microsoft.com> wrote in message
> > news:e92SDZ0uCHA.2000@TK2MSFTNGP11...
> > > It's been moved to the registry

> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.0\NativeDE\StepOver]

> > > "10"=".*CString.*=NoStepInto"

> > > "15"="ATL\\:\\:.*=NoStepInto"

> > > "Michal Bacik" <mic...@lonelycatgames.com> wrote in message
> > > news:erc$sIvuCHA.1848@TK2MSFTNGP09...
> > > > Hi,
> > > > I'm slowly moving to .NET version of Visual Studio, porting all my
> > > behaviors
> > > > from MSVC 6.0.
> > > > Anyway, when I edit autoexp.dat file, the [ExecutionControl] section
> > seems
> > > > not to work anymore.

> > > > I've used this:
> > > > [ExecutionControl]
> > > > C_str::* = NoStepInto
> > > > Anyway debugger always steps into C_str class' methods.

> > > > I know this is undocumented, but automatic expansion in the
> autoexp.dat
> > > > works fine on .NET.
> > > > Any idea how to prevent debugger stepping into specific
> > functions/classes?
> > > > Thanks,
> > > > - Michal

Reply to author Forward