[IronPython] IronPython 2.0 Alpha 1 on Mono

[M. David Peterson]

BTW... for those keeping score, as Seo proclaimed, IP 2.0A1 will now
successfully build on Mono (SVN r77275).  I have my doubts the stacktrace
will be all that useful to anyone, but you never know, so for what its
worth,

[mdavid at domU-12-31-37-00-03-10 Debug]$ mono ipy.exe
> Stacktrace:
>
>   at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(bool) <0x00004>
>   at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(bool) <0xfffffff>
>   at System.Reflection.Assembly.GetExportedTypes () <0x0000c>
>   at Microsoft.Scripting.ReflectedPackage.LoadTypesFromAssembly (
> System.Reflection.Assembly) <0x00071>
>   at Microsoft.Scripting.TopReflectedPackage.LoadAssembly (
> System.Reflection.Assembly) <0x0003d>
>   at Microsoft.Scripting.ClrModule.AddReference (
> System.Reflection.Assembly) <0x0004a>
>   at Microsoft.Scripting.ClrModule.AddReference (object) <0x00035>
>   at Microsoft.Scripting.ClrModule.AddReference (object[]) <0x0003a>
>   at IronPython.Runtime.SystemState.InitializeBuiltins () <0x00075>
>   at IronPython.Runtime.SystemState..ctor (
> Microsoft.Scripting.Hosting.ScriptEngine,IronPython.Runtime.Importer)
> <0x0005d>
>   at IronPython.Hosting.PythonEngine..ctor (
> IronPython.Hosting.PythonLanguageProvider,IronPython.PythonEngineOptions)
> <0x00089>
>   at IronPython.Hosting.PythonEngine.<>c__AnonymousMethod0 (
> IronPython.Hosting.PythonLanguageProvider,IronPython.PythonEngineOptions)
> <0x0001f>
>   at (wrapper delegate-invoke)
> System.MulticastDelegate.invoke_PythonEngine_PythonLanguageProvider_PythonEngineOptions(
> IronPython.Hosting.PythonLanguageProvider,IronPython.PythonEngineOptions)
> <0xffffffff>
>   at Microsoft.Scripting.Hosting.SingletonEngineFactory`3.GetInstance (
> IronPython.Hosting.PythonLanguageProvider,IronPython.PythonEngineOptions)
> <0x000a8>
>   at IronPython.Hosting.PythonLanguageProvider.GetEngine (
> Microsoft.Scripting.EngineOptions) <0x0005a>
>   at
> Microsoft.Scripting.Hosting.LanguageProvider.Microsoft.Scripting.Hosting.IL
> anguageProvider.GetEngine (Microsoft.Scripting.EngineOptions) <0x0000e>
>   at Microsoft.Scripting.Hosting.ConsoleHost.RunCommandLine (
> Microsoft.Scripting.OptionsParser) <0x00089>
>   at Microsoft.Scripting.Hosting.ConsoleHost.ExecuteInternal () <0x0026d>
>   at Microsoft.Scripting.Hosting.ConsoleHost.Execute () <0x0009b>
>   at Microsoft.Scripting.Hosting.ConsoleHost.Run (string[]) <0x00143>
>   at PythonConsoleHost.Main (string[]) <0x00025>
>   at (wrapper runtime-invoke) System.Object.runtime_invoke_int_string[]
> (object,intptr,intptr,intptr) <0xffffffff>
>
> Native stacktrace:
>
>         mono [0x8143e83]
>         mono [0x81300b6]
>         [0xbfffe440]
>         mono [0x80dc1f0]
>         mono(mono_class_get_full+0x99) [0x80dbb55]
>         mono(mono_class_get+0x13) [0x80dbcd3]
>         mono [0x8094d8b]
>         mono [0x8095089]
>         [0xb6f4596c]
>         [0xb6f45925]
>         [0xb6f45832]
>         [0xb6f453a6]
>         [0xb6f47843]
>         [0xb6f4771e]
>         [0xb6f47683]
>         [0xb7015fde]
>         [0xb7014f1e]
>         [0xb70147b2]
>         [0xb7014358]
>         [0xb7014305]
>         [0xb7014131]
>         [0xb701402b]
>         [0xb7012b5f]
>         [0xb7012802]
>         [0xb7012066]
>         [0xb7011d0c]
>         [0xb7495784]
>         [0xb74951e6]
>         [0xb7495074]
>         mono(mono_runtime_exec_main+0x151) [0x808b2e1]
>         mono(mono_runtime_run_main+0x1f0) [0x808b584]
>         mono(mono_main+0xf27) [0x8058f9b]
>         mono [0x8057c0f]
>         /lib/tls/libc.so.6(__libc_start_main+0xcf) [0xb7d7c23f]
>         mono [0x8057b71]
>
> =================================================================
> Got a SIGSEGV while executing native code. This usually indicates
> a fatal error in the mono runtime or one of the native libraries
> used by your application.
> =================================================================
>
> Aborted
>

On 5/11/07, M. David Peterson <xmlhacker at gmail.com> wrote:
>
> Do I understand correctly: IP 2.0, and therefore the DLR, will now compile
> on Mono, and as such, it is now possible to begin the process of trying to
> break it?  This would be fantastic! :D
>
> (/me is building Mono from SVN, hopes to have successfully built IP 2.0soon thereafter...)
>
> On 5/11/07, Sanghyeon Seo <sanxiyn at gmail.com> wrote:
> >
> > 2007/5/2, Sanghyeon Seo <sanxiyn at gmail.com>:
> > > Here's my first try on building IronPython 2.0 Alpha 1 on Mono:
> > > https://fepy.svn.sourceforge.net/svnroot/fepy/trunk/patches/2.0a1/
> > > (snip)
> >
> > Mono revision later than 77232 compiles IronPython 2.0 Alpha 1 without
> > any modifications besides makefile patch.
> >
> > So, in short, you can forget about this. :-)
> >
> > I will briefly look at what I can do to make it work with Mono
> > 1.2.2.1. This is a personal convinience, as it is the version that
> > shipped with the Debian stable release.
> >
> > --
> > Seo Sanghyeon
> > _______________________________________________
> > users mailing list
> > users at lists.ironpython.com
> > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
> >
>
>
>
> --
> /M:D
>
> M. David Peterson
> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
> http://dev.aol.com/blog/3155




-- 
/M:D

M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20070511/ad2b865f/attachment.html>