I attached to the process but it still didn't trap the error.  It just
died.

The event viewer has the following information

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/
event">
- <System>
  <Provider Name=".NET Runtime" />
  <EventID Qualifiers="0">1023</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2008-10-08T16:40:23.000Z" />
  <EventRecordID>5246</EventRecordID>
  <Channel>Application</Channel>
  <Computer>blackpc</Computer>
  <Security />
  </System>
- <EventData>
  <Data>.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine
Error (6B775E00) (80131506)</Data>
  </EventData>
  </Event>



On Oct 3, 8:53 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote:
> You can revert to the Gallio Alpha 3 Update 3, but that's not an ideal
> long-term solution.
> We need to understand what's causing those crashes because I haven't seen
> them before.
>
> First, look in the Windows Event Log.
> I expect you'll find the last dying gasps of Visual Studio recorded there.
>
> After doing that, please try this:
>
> 1. Launch an instance of Visual Studio and open your Solution.
>
> 2. Launch another instance of Visual Studio and use the Debug -> Attach
> Process option to attach to the other instance of Visual Studio
> (devenv.exe).
>
> 3. Now play with your Solution in the previous instance and try to reproduce
> the crash.
>
> 4. When it crashes, hopefully you'll get some useful output in the debugger.
> If you don't see anything at all, ensure that you disable the "Just my Code"
> option but enable the "Exception Assistant" option in the Visual Studio
> Debugger Options tab.  Then try again.
>
> Let me know what you find.
>
> I expect the root cause is a StackOverflowException or perhaps an
> ExecutionEngineException.  But we need more information to pin down the
> origin.
>
> Jeff.
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On
>
> Behalf Of Emad Ibrahim
> Sent: Thursday, October 02, 2008 11:12 PM
> To: MbUnit.User
> Subject: MbUnit Re: visual studio crash
>
> Thanks for getting back...
>
> Which version should i go back to?  I can't remember the last working
> version i had installed...
>
> On Oct 3, 2:09 am, "Jeff Brown" <[EMAIL PROTECTED]> wrote:
> > I'm currently busy working on a stable version for release.
> > It's actually quite good now but there is a regression in the TDNet
> > support.  Meanwhile there have been many improvements in the R#
> > support, which may have been partly responsible for the crashes you
> observed.
>
> > Jeff.
>
> > On Thu, Oct 2, 2008 at 9:24 PM, Emad Ibrahim <[EMAIL PROTECTED]> wrote:
>
> > > Damn... it is doing it again...   I need help.  Which version is
> > > stable?  Should I reinstall resharper and td.net as well?
>
> > > What is the right order to re-install all this?
>
> > > -Emad
>
> > > On Oct 2, 6:16 pm, Emad Ibrahim <[EMAIL PROTECTED]> wrote:
> > > > Weired...  It just stopped doing that...  I created a new project
> > > > and opened an aspx page fine then I closed and opened the project
> > > > that was crashing and it works now... weird!!!
>
> > > > On Oct 2, 6:13 pm, Emad Ibrahim <[EMAIL PROTECTED]> wrote:
>
> > > > > I uninstalled gallio and installed the latest version
> > > > > fromhttp://
>
> ccnet.gallio.org/Distributables/(3.0.4.449)<http://ccnet.gallio.org/Distribu
> tables/%283.0.4.449%29>.
> > >  Now whenever I
> > > > > try to open any aspx or ascx page, visual studio just dies.  No
> > > > > error, nothing.  It just disappears.
>
> > > > > I removed gallio and everything worked fine..  Reinstalled it.  
> > > > > It crashed again...
>
> > > > > Help!!!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to