[Mono-dev] 21 test(s) did not pass.

Hello, In my FreeBSD-amd64 box, many checks of mono svn trunk failed. Mostly are caused by these day's changes. $ gmake check ...(snip)... 362 test(s) passed. 21 test(s) did not pass. Failed tests: test-dup-mp.exe appdomain.exe appdomain1.exe appdomain2.exe appdomain-unload.exe appdomain-async-

[Mono-dev] StyleCop incompatibility

The MS defines a code-style rule for the order in which the ³usings² must be sorted: http://www.thewayithink.co.uk/stylecop/sa1208.htm The MonoDevelop application¹s ³Sort Usings² functionality simply sorts using in the alphabetical order but does not consider this rule. Related problems: How does

Re: [Mono-dev] 21 test(s) did not pass.

I don't believe the FreeBSD-amd64 port is functional or properly regression tested since we don't have a OSX 64bits port. OSX 32bits does great good in keeping FreeBSD x86 working, so I suppose the same applies for amd64. On Tue, Dec 8, 2009 at 7:58 AM, KISHIMOTO, Makoto wrote: > Hello, > > In

[Mono-dev] Fwd: 21 test(s) did not pass.

Sorry, I forgot to post this on the list as well. -- Forwarded message -- From: Mark Probst Date: Tue, Dec 8, 2009 at 11:42 AM Subject: Re: [Mono-dev] 21 test(s) did not pass. To: "KISHIMOTO, Makoto" Cc: Zoltan Varga On Tue, Dec 8, 2009 at 10:58 AM, KISHIMOTO, Makoto wrote: >

Re: [Mono-dev] StyleCop incompatibility

According to the rule - any using statement starting with "System." should be sorted first. It's nothing to do with the assembly that the namespace comes from. Alan. On Tue, Dec 8, 2009 at 11:27 AM, Andrew Mikhailov wrote: > The MS defines a code-style rule for the order in which the “usings”

[Mono-dev] [patch] ILGenerator.Emit(OpCode, LocalBuilder) with non variable related opcode

Hey, .NET's ILGenerator allows contructions such as: il.Emit (OpCodes.Nop, local_builder); We're currently translating that into a ldloc, while .net actually emits the nop. The attached patch fixes this. Please review, thanks. -- Jb Evain Index: System.Reflection.Emit/ILGenerator.cs ===

[Mono-dev] Foreing thread lifecycle tracking

Hello, I am starting this thread in order to find a solution to an issue encountered with Mono and described in this bug entry (https://bugzilla.novell.com/show_bug.cgi?id=537764). Short Summary: On Mac OS X, Mono is using POSIX pthread functions to hook to TSD (Thread Specific Data) in order to

[Mono-dev] SIGSEGV when using WeakReferences in multi-threaded application

Hi, I am starting this thread, as we filed a bug at Bugzilla five month ago but there was no solution for the problem yet. A simplified test case was created and is attached to the bug entry which can be found at https://bugzilla.novell.com/show_bug.cgi?id=522233 Hope there is someone out there t

[Mono-dev] Mono and explicit null checking (AIX platforms).

Hello, Developers that have tried to port Mono to AIX have ran into the problem that AIX keeps a valid page at address zero, which means that it is not possible to properly generate the NullReferenceException. Mono on SVN currently contains a --debug option that can be used to insert expl

Re: [Mono-dev] SIGSEGV when using WeakReferences in multi-threaded application

Hi, Sorry about that. I tried debugging it back then, but couldn't find out the cause of the problem, it seemed like memory corruption inside the GC data structures. Zoltan On Tue, Dec 8, 2009 at 7:09 PM, Daniel Weuthen < daniel.weuthen...@deepinvent.com> wrote: > Hi, > > I a

[Mono-dev] [PATCH] IOMAP reporting - reimplemented as a profiler module

Hello, Attached is a new version of the IOMAP reporting patch which moves all the code to a dynamically loadable profiler module. The "report" option from MONO_IOMAP is thus gone, but all the functionality remains the same. Please review and let me know if it's OK to commit marek diff

Re: [Mono-dev] build fails on genmdesc

2009/12/4 Gerard Braad : > Currently trying to get Mono packaged for Maemo 5 (and the N900). > Unfortunately I encounter some issues. > > I try to build Mono 2.4.2.3 in scratchbox using the host-gcc, but the > build fails on ./genmdesc ./cpu-x86.md cpu-x86.h x86_desc > with a make: *** [cpu-x86.h]

Re: [Mono-dev] WaitAny does not consistently return when waiting on more than one WaitHandle

I¹ve finally gotten around to creating a Bugzilla case for this: https://bugzilla.novell.com/show_bug.cgi?id=561792 Thanks, Tom On 11/25/09 3:59 PM, "Tom Philpot" wrote: > Zoltan, > > Would it help if I created a Mac OS specific bugzilla? Is there someone else > that can test this on Mac? (Geo

[Mono-dev] Internal-Call

Having read all the embeded and script features of mono, I want to use C# instead of Lua as the script language while the host language is C++ in my project. I want to use C#( managed code ) to call the functions which exposed from C++ using internal-call approach, and i want to call the instance