# Thursday, April 17, 2008
« New Development Snapshot | Main | IKVM 0.36 Update 2 Release Candidate 1 »
Invalid Casting Goodness

Yesterday Miguel blogged about a nice new feature in Mono. I added the IKVM_VERBOSE_CAST environment variable to IKVM to do something similar a while ago.

public class test {
  public static void main(String[] args) {

C:\j>\ikvm-\bin\ikvm test
Exception in thread "main" java.lang.ClassCastException
        at test.main(test.java)


C:\j>\ikvm-\bin\ikvm test
Exception in thread "main" java.lang.ClassCastException: Object of type "System.String[], mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" cannot be cast to "System.String, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
        at test.main(test.java)

Note that the assembly qualified type names are displayed, as I believe this feature is particularly useful when trying to debug issues that arise from having loaded multiple assemblies that contain the "same" types.

While writing this I discovered that both JDK 1.6 and .NET 2.0 always generate descriptive exception messages for invalid casts:

C:\j>\jdk1.6\bin\java test
Exception in thread "main" java.lang.ClassCastException: [Ljava.lang.String; can not be cast to java.lang.String
        at test.main(test.java:5)

C:\j>\ikvm\bin\ikvm test
Exception in thread "main" java.lang.ClassCastException: Unable to cast object of type 'System.String[]' to type 'System.String'.
        at test.main(test.java:5)

This last result is my local ikvm development version running on .NET 2.0 with a patch to enable taking the exception message from the .NET InvalidCastException, which I didn't previously do because on .NET 1.1 this message didn't contain any useful information.

Thursday, April 17, 2008 8:51:38 AM (W. Europe Daylight Time, UTC+02:00)  #    Comments [2]
Saturday, April 19, 2008 4:10:46 PM (W. Europe Daylight Time, UTC+02:00)
I think it would have been slightly more useful if the assembly information included the assembly location. There's a fairly common case when you load the same assembly from two different locations (once in the load context and once in the load-from context, I've blogged about it in the past), so the assembly qualified names would appear identical...
Saturday, April 19, 2008 5:48:01 PM (W. Europe Daylight Time, UTC+02:00)
That's a good point. I will improve the message to include the location if the assembly names are identical. The load context and load-from context issue is trickier, because AFAIK there is no way to determine in what context an assembly was loaded.
Home page

I apologize for the lameness of this, but the comment spam was driving me nuts. In order to be able to post a comment, you need to answer a simple question. Hopefully this question is easy enough not to annoy serious commenters, but hard enough to keep the spammers away.

Anti-Spam Question: What method on java.lang.System returns an object's original hashcode (i.e. the one that would be returned by java.lang.Object.hashCode() if it wasn't overridden)? (case is significant)

Comment (HTML not allowed)  

Live Comment Preview