Comment 41 for bug 1064804

Revision history for this message
Simone Busoli (simone.busoli) wrote : Re: [Nunit-core] [Bug 1064804] Re: Test throws an exception in NUnit but works when running in MSTest or as a Console application

Hi Mun,

not enough I'm afraid as it looks like a minidump rather than a full dump.
In any case I doubt it will be useful, I did a bit of research and I'm not
sure analyzing it will give us any clue of what's going on. I believe the
very best thing we could do is experiment, but it takes time especially as
we don't have access to that code and cannot reproduce the problem.

In any case one somewhat simple thing you could do is compile nunit for
.net 4.0 and try to run your tests with it, after you compile them and your
production code for .net 4.0 too. Since these kind of exceptions might be
related to the CLR itself (although quite unlikely) it might be something
which in CLR 4 went away.
To compile NUnit for 4.0 pull the code from launchpad with a bazaar client
and just run build net-4.0 in the root folder.

Simone

On Fri, Oct 12, 2012 at 11:52 AM, Mun Wai Chan
<email address hidden>wrote:

> Here you go.
>
> ** Attachment added: "nunit-console-x86_121012_105550.dmp"
>
> https://bugs.launchpad.net/nunitv2/+bug/1064804/+attachment/3396099/+files/nunit-console-x86_121012_105550.dmp
>
> --
> 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~nunit-core
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~nunit-core
> More help : https://help.launchpad.net/ListHelp
>