← Back to team overview

nunit-core team mailing list archive

[Bug 1064804] Re: Test throws an exception in NUnit but works when running in MSTest or as a Console application

 

Does this help?

E:\New folder (3)>procdump.exe -ma -e 1 -f "" -x "e:\New folder (3)" "c:\Program
 Files (x86)\NUnit 2.6.1\bin\nunit-x86.exe"

ProcDump v5.00 - Writes process dump files
Copyright (C) 2009-2012 Mark Russinovich
Sysinternals - www.sysinternals.com
With contributions from Andrew Richards

Process:               nunit-x86.exe (26956)
CPU threshold:         n/a
Performance counter:   n/a
Commit threshold:      n/a
Threshold seconds:     n/a
Number of dumps:       1
Hung window check:     Disabled
Exception monitor:     First Chance+Unhandled
Exception filter:      Display Only
Terminate monitor:     Disabled
Dump file:             e:\New folder (3)\nunit-x86.dmp


Press Ctrl-C to end monitoring without terminating the process.

CLR Version: v2.0.50727

[10:59:29] Exception: 80000003.BREAKPOINT
[10:59:29] Exception: 80000004.SINGLE_STEP
[10:59:29] Exception: 80000003.BREAKPOINT
[10:59:39] Exception: 000006BA
[10:59:42] Exception: E06D7363.PAVEEFileLoadException@@
[10:59:42] Exception: E06D7363.msc
[10:59:42] Exception: E06D7363.PAVEEFileLoadException@@
[10:59:42] Exception: E06D7363.msc
[10:59:42] Exception: E06D7363.PAVEEFileLoadException@@
[10:59:42] Exception: E06D7363.msc
[10:59:42] Exception: E06D7363.PAVEEFileLoadException@@
[10:59:42] Exception: E0434F4D.System.IO.FileNotFoundException
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000004.SINGLE_STEP
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000004.SINGLE_STEP
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000004.SINGLE_STEP
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000004.SINGLE_STEP
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:45] Exception: 80000003.BREAKPOINT
[10:59:47] Exception: 000006D9
[10:59:47] Exception: 000006D9
[10:59:48] Exception: C0000005.ACCESS_VIOLATION
The process has exited.

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1064804

Title:
  Test throws an exception in NUnit but works when running in MSTest or
  as a Console application

Status in NUnit V2 Test Framework:
  New

Bug description:
  Hi,

  I have a simple test which throws an error when I run it using NUnit
  (fails on both NUnit GUI/console and Resharper in VS). However, if ran
  using Visual Studio's Test -> Debug option or as a Console
  application, it runs fine. The code is exactly the same for the 3
  different projects types (NUnit, Console and MSTest).

  Source code for NUnit test:

  using System.Net;
  using Microsoft.Dynamics.BusinessConnectorNet;
  using Microsoft.VisualStudio.TestTools.UnitTesting;

  namespace TestProject1
  {
      [TestClass]
      public class UnitTest1
      {
          [TestMethod]
          public void TestMethod1()
          {
              Axapta ax = new Axapta();
              ax.LogonAs("User1", "Globe", new NetworkCredential("User1", "pwd", "Globe"), default(string),                       default(string), "A6BuildTestAos:6004", default(string));
               ax.Logoff();
          }
      }
  }

  Error:

  FatalExecutionEngineError was detected.
  The runtime has encountered a fatal error. The address of the error was at 0x5785ca87, on thread 0x792c. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1064804/+subscriptions


Follow ups

References