[Mono-bugs] [Bug 735999] New: crash on instantiating a class whose inheritance chain differs between target & runtime SDKs

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Dec 9 14:55:46 EST 2011


https://bugzilla.novell.com/show_bug.cgi?id=735999

https://bugzilla.novell.com/show_bug.cgi?id=735999#c0


           Summary: crash on instantiating a class whose inheritance chain
                    differs between target & runtime SDKs
    Classification: Mono
           Product: MonoDroid
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Runtime
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: adam.lickel at rd.io
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=466815)
 --> (http://bugzilla.novell.com/attachment.cgi?id=466815)
Stack Trace, Mono & Java Test Cases

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2)
AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7

I know of two instances at least:
LinkMovementMethod, MotionEvent

When built with Honeycomb and Gingerbread (respectively) these classes cannot
be instantiated on a downlevel version of the OS. This is perfectly legal in
Java as the class exists in both the build & runtime.
The only difference is that the inheritance chain was modified to add a new
base class. 

In MonoDroid I see a TargetInvocationException about how that base class does
not exist (see attached).

I also attached source projects for both java & monodroid which should behave
similarly.

Reproducible: Always

Steps to Reproduce:
1.Call LinkMovementMethod.Instance
2.Build with Honeycomb
3.Run on Gingerbread (etc)
Actual Results:  
The activity crashes

Expected Results:  
The activity successfully creates the object

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the mono-bugs mailing list