[Mono-dev] .Net 2.0 code failing on mono

[Zoltan Varga]

                                          Hi,

  The next mono release after 1.1.10 will have some logging code added so
running your app with the MONO_LOG_LEVEL env variable set to 'debug'
will show which class/method is missing.

                      Zoltan

On 11/11/05, Ben Maurer <bmaurer at ximian.com> wrote:
> Hey,
>
> On Thu, 2005-11-10 at 16:19 -0700, Ron Vered wrote:
> > My company is not officially supporting mono and some client WinForms
> > code was built for .net 2.0.
> >
> > With my limited bandwidth, I would like to help the cause of mono to
> > make this code run also on mono.
> >
> > When naively running the client app with mono (1.1.9.2) I get a
> > dialougue with
> > ** ERROR **: file class.c line 2233 (mono_class_setup_parent): should
> > not be reached aborting...
> > With no additional information about the problem.
> >
> > Guessing it maybe related to missing assemblies / implementation, I
> > have tried:
> > mono --trace=M:Assembly:GetTypes
> > which produces no information.
>
> The lines in question look like:
>         if (!MONO_CLASS_IS_INTERFACE (class)) {
>                 class->parent = parent;
>
>                 if (!parent)
>                         g_assert_not_reached (); /* FIXME */
>
> This code looks like it is trying to initialize the parents of the class
> being setup. Maybe you are inheriting from a new 2.0 class that we have
> not created?
>
> I'd first try compiling your program with gmcs. If there are classes
> that we don't have, it should be more easily apparent there.
>
> -- Ben
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>