tracking weird crash with monodoc

Rafael Ferreira <[email protected]>
Newsgroups gmane.comp.gnome.mono.documentation
Message-ID <[email protected]>
Hey guys, 

Every once in a while the docbrowser crashes on me throwing the
following exception:

Unhandled Exception: System.InvalidCastException: Cannot cast from
source type to destination type.
in <0x00149> GLib.ObjectManager:CreateObject (IntPtr raw)
in <0x000c1> GLib.Object:GetObject (IntPtr o, Boolean owned_ref)
in <0x0000c> GLib.Object:GetObject (IntPtr o)
in <0x0002e> Gtk.Label:get_Layout ()
in [0x00002]
(at /home/rafael/dev/mono-svn/mono-tools/docbrowser/elabel.cs:60)
ELabel:Reload ()
in [0x00008]
(at /home/rafael/dev/mono-svn/mono-tools/docbrowser/elabel.cs:38)
ELabel:set_Text (System.String value)
in [0x00068]
(at /home/rafael/dev/mono-svn/mono-tools/docbrowser/browser.cs:594)
Monodoc.Browser:Render (System.String text, Monodoc.Node matched_node,
System.String url)
in [0x0007a]
(at /home/rafael/dev/mono-svn/mono-tools/docbrowser/browser.cs:1674)
Monodoc.TreeBrowser:RowActivated (System.Object sender, System.EventArgs
a)
in (wrapper delegate-invoke)
System.MulticastDelegate:invoke_void_object_EventArgs
(object,System.EventArgs)
in <0x000c1> GtkSharp.voidObjectSignal:voidObjectCallback (IntPtr arg0,
Int32 key)
in (wrapper native-to-managed)
GtkSharp.voidObjectSignal:voidObjectCallback (intptr,int)
in <0x00000> <unknown method>
in (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00007> Gtk.Application:Run ()
in [0x001a8]
(at /home/rafael/dev/mono-svn/mono-tools/docbrowser/browser.cs:104)
Monodoc.Driver:Main (System.String[] args)

Can anyone give me some pointers on how I can fix this? And no, I cannot
come up with a reproducible test case. Btw, I'm on monodoc/doctools from
svn. 

- raf


_______________________________________________
Mono-docs-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-docs-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.