Hi Jimmy,

Can you switch to using the F# CTP? This is a difference specific to the .NET 1.x profile that used to be used under Mono in version 1.9.4 and before

Thanks

Don

By on 9/9/2008 4:05 PM ()

Hi Don,

Thanks for the reply. I've installed the CTP and tried it out, and so far with both Mono 1.2.x and 1.9.1 I get impressive looking segfaults and heap dumps and that sort of thing. Here's a sampling:

#17 0x080bfedb in mono_metadata_parse_mh_full (m=0x828d048,
container=0x829d42c, ptr=0xb6ad2db4 "\0230\006") at metadata.c:2875
#18 0x080ca342 in mono_get_method_from_token (image=0x828d048,
token=<value optimized out>, klass=<value optimized out>, context=0x0,
used_context=0xbfd9bc38) at loader.c:1407
...
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Normal C# apps still compile and run in my Mono 1.9.1 environment, and my old F# 1.9.4.x build still runs OK. Any clues as to what might be happening? I saw another post about problems in Mono, but never saw any result other than a suggestion to install the latest Mono.

Thanks,

Jimmy

By on 9/10/2008 12:04 PM ()

The recommendation in the CTP release notes is to use the Mono 2.0 Preview.

Kind regards

don

By on 9/11/2008 2:56 AM ()

Hi Don,

Ah, I saw only one download on the Mono page, and it said "Latest Version: 1.9.1 (Mono 2.0 Beta)" so I got confused. Sorry for the trouble, and thanks for the help.

Jimmy

By on 9/11/2008 4:01 AM ()

PS - moving to the Mono 2.0 Preview made it work.

By on 9/11/2008 10:20 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper