Hi Dave-

I was able to narrow down the problem.  If I make a new project
(default win32 console application) and paste the following code into
the .cpp file containing the default implementation of "main()"(ie,
just replace everything in that file with this)

-------------------- begin cut ------------------

// crash2.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"

int _tmain(int argc, _TCHAR* argv[])
{
    return 0;
}

namespace BAZ
{

I32 Foo(Bar *byzA, Bar *byzB, Rame *res)
{
}

void Foo(Bar *in_byz, Bop *mosh, Bip *bip)
{
}

void Foo(Bar *in_byz, Bip *bip)
{
 Foo(&bez, (Bop *)jojo, bip);
}

} // namespace BAZ

-------------------------  end cut -------------------------------

Then here are the steps to cause the hang (I tested this on a few other
people's .NET installations here as well)

1)  Find the line "Foo(&bez, (Bop *)jojo, bip);"
2)  Double click the word "Foo" part the function name is hilited
3)  Press "control f" to initialize the find dialog  -OR- right click
on the selected "Foo" string and then select "Go To Definition" (I have
the option to initialize the find dialog based on what is hilited, so
that might be part of the reason it crashes when i hit "control-f" --
not positive about that though)
4)  Sit and wonder why .NET is hanging and if it is a part of
microsoft's secure computing initiative

Like I said, I've tried this on multiple different computers here and
it hangs on all of them..   The key part seems to be the fact that the
functions are sitting inside the namespace-- if I remove the namespace,
then it doesn't cause a hang.

Are you able to reproduce this at all on your end?  I'm still trying to
find an option somewhere that will prevent the hang... argh!

And just to be complete, here is the version info in the "About" window
for my visual studio .net install:

Microsoft Development Environment 2003 Version 7.1.3088
Microsoft .NET Framework 1.1 Version 1.1.4322 SP1
Microsoft Visual C++ .NET   69462-112-0090057-18350

-sam