Subject: Problem starting MD on Ubuntu Edgy - msg#00062

List: gnome.mono.monodevelop.general

Date: Prev Next Index Thread: Prev Next Index

Hi all,

I did a fresh install of Dapper then upgraded to Edgy. After doing so
MD crashes when starting: I get the splash screen then it dies. I'll
post the output below. Once I found that the Ubuntu package wasn't
working for me I built mono and MD from svn myself but am still
getting the same errors.

does "** ERROR **: file class.c: line 2049
(mono_class_setup_vtable_general): should not be reached" mean
anything to anyone?

Anybody know what's going on exactly and/or how to fix it?

Thanks in advance,
Chris

##START PROGRAM OUTPUT

chris@chris-laptop:~/programming/src/svn/monodevelop$ make run
cd build/bin && LD_LIBRARY_PATH=`echo ":/usr/lib/mozilla" | sed
's/^://g'` /usr/bin/mono --debug MonoDevelop.exe
no implementation for interface method
MonoDevelop.Ide.Codons.IDisplayBinding::get_DisplayName() in class
MonoDevelop.XmlEditor.XmlDisplayBinding
METHOD .ctor()
METHOD CanCreateContentForMimeType(string)
METHOD CreateContentForMimeType(string,System.IO.Stream)
METHOD CanCreateContentForFile(string)
METHOD CreateContentForFile(string)

** ERROR **: file class.c: line 2049
(mono_class_setup_vtable_general): should not be reached
aborting...

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes
(bool) <0x00004>
at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes
(bool) <0xffffffff>
at System.Reflection.Assembly.GetTypes () [0x00000] in
/build/buildd/mono-1.1.17.1/mcs/class/corlib/System.Reflection/Assembly.cs:322
at MonoDevelop.Core.AddIns.DefaultAddInTree.LoadCodonsAndConditions
(System.Reflection.Assembly) [0x00000] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/DefaultAddInTree.cs:233
at MonoDevelop.Core.AddIns.DefaultAddInTree.LoadAssembly (string)
[0x00039] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/DefaultAddInTree.cs:220
at MonoDevelop.Core.AddIns.AddIn.AddRuntimeLibraries
(string,System.Xml.XmlElement) [0x00085] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddIn.cs:251
at MonoDevelop.Core.AddIns.AddIn.ReadXmlContents
(string,System.Xml.XmlElement) [0x0004f] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddIn.cs:220
at MonoDevelop.Core.AddIns.AddIn.Initialize (string) [0x00113] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddIn.cs:209
at MonoDevelop.Core.AddIns.AddInTreeSingleton.InsertAddIn (string)
[0x00006] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddInTreeSingleton.cs:53
at MonoDevelop.Core.AddIns.AddInService.PreloadAddin
(MonoDevelop.Core.IProgressMonitor,string) [0x000d4] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddInService.cs:207
at MonoDevelop.Core.AddIns.AddInService.PreloadAddins
(MonoDevelop.Core.IProgressMonitor,string[]) [0x0015b] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddInService.cs:169
at MonoDevelop.Ide.Gui.IdeStartup.Run (string[]) [0x002b5] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Ide/MonoDevelop.Ide.Gui/IdeStartup.cs:140
at MonoDevelop.Core.AddIns.AddInService.StartApplication
(string,string[]) [0x00093] in
/home/chris/programming/src/svn/monodevelop/Core/src/MonoDevelop.Core/MonoDevelop.Core.AddIns/AddInService.cs:127
at MonoDevelop.Startup.SharpDevelopMain.Main (string[]) <0x00039>
at (wrapper runtime-invoke)
System.Object.runtime_invoke_int_string[]
(object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

/usr/bin/mono(mono_handle_native_sigsegv+0xde) [0x815644e]
[0xffffe440]
/lib/tls/i686/cmov/libc.so.6(abort+0x103) [0x40150ef3]
/usr/lib/libglib-2.0.so.0(g_logv+0x4c2) [0x4006f122]
/usr/lib/libglib-2.0.so.0(g_log+0x29) [0x4006f159]
/usr/lib/libglib-2.0.so.0(g_assert_warning+0x76) [0x4006f1d6]
/usr/bin/mono [0x80f1ba2]
/usr/bin/mono [0x80f226a]
/usr/bin/mono(mono_class_init+0x62d) [0x80f28dd]
/usr/bin/mono(mono_type_get_object+0x96) [0x815f946]
/usr/bin/mono [0x80a10bc]
/usr/bin/mono [0x80a2c80]
[0x41523dbb]
[0x41523d75]
[0x41523bb4]
[0x414abeb6]
[0x414abc72]
[0x414ab9a7]
[0x414ab2fb]
[0x414aad08]
[0x4148abaf]
[0x42a98fda]
[0x4153556d]
[0x413c74ed]
[0x40b10b42]
[0x40b10a84]
/usr/bin/mono(mono_runtime_exec_main+0x9f) [0x80996ef]
/usr/bin/mono(mono_runtime_run_main+0x1b9) [0x8099999]
/usr/bin/mono(mono_main+0xe47) [0x805d477]
/usr/bin/mono [0x805c122]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0x4013b8cc]
/usr/bin/mono [0x805c071]
/bin/bash: line 1: 13915 Aborted (core dumped)
LD_LIBRARY_PATH=`echo ":/usr/lib/mozilla" | sed 's/^://g'`
/usr/bin/mono --debug MonoDevelop.exe
make: *** [runmd] Error 134

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

Re: Managed Line Editor

Il giorno mar, 31/10/2006 alle 11.09 +0100, Matej Urbas ha scritto: > I haven't been able to figure out much yet (will have to do much more > research before jumping into the code), but I think I've figured that > there are two basically distinct approaches to underlying text buffers: > > - One where all the text is in a simple array You can discover which editor uses this method by loading a file with pretty long lines (say 1000 chars): it usually slows down to turtle crawl during any insert/delete operation. Ok, nobody actually write such long lines but sometimes you open a file with wrong end-line marker and having to kill the editor because it has become unusable doesn't make me happy. So I am all in favour of line-segmented or even arbitrary-chunk-segmented editors. federico -- Federico Di Gregorio http://people.initd.org/fog Debian GNU/Linux Developer fog@xxxxxxxxxx INIT.D Developer fog@xxxxxxxxx All programmers are optimists. -- Frederick P. Brooks, Jr. signature.asc Description: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio firmata digitalmente _______________________________________________ Monodevelop-list mailing list Monodevelop-list@xxxxxxxxxxxxxxxx http://lists.ximian.com/mailman/listinfo/monodevelop-list

Next Message by Date: click to view message preview

Re: Managed Line Editor

> I'm more in favour of line-segmented buffers - mostly because of faster > line searching and text insertion. Agreed, for the reasons you enumerated. -- Tcsh: Now with higher FPS! http://www.gnu.org/philosophy/shouldbefree.html

Previous Message by Thread: click to view message preview

Managed Line Editor

Hi for a long time now, I've been planning to somehow improve MD's source editing experience with various kinds of coding assistance techniques. Still, I have been only investigating - I have yet to do some coding... I have looked into various IDEs: Eclipse, NetBeans and VS.NET 2005, and the first thing I noticed about them is that they all have specially crafted editors - to perfectly integrate into the IDE and to suit all their needs. Also, for a while, I've been looking into GtkSourceView's internals - in order to help adding new features we'd need at MonoDevelop... Soon it became clear that I'd have to be a dedicated GTK expert to even dare dream about adding any kind of new features (not to mention the effort needed to make new features available to Mono apps)... Anyways, I don't see myself working on GtkSourceView - ever... However, I'm more and more fond of the idea to create an editor designed specifically for MonoDevelop (or any other Mono app). Create a source editor with GTK# and Pango? Take a look at how SharpDevelop's, NetBeans' or Eclipse's (my favourite) editors manage things? Better integrate parsers with editors? Lluis, is this a sane idea? Enjoy, --- Matej

Next Message by Thread: click to view message preview

Re: Problem starting MD on Ubuntu Edgy

Hi Chris, Looks like you have the old XML Editor add-in (v0.1) installed which does not work with newer versions of MonoDevelop. I believe you can remove it by running "mdtool gsetup". Alternatively you can remove the folder ~/.config/MonoDevelop/addins/MonoDevelop.XmlEditor_0.1.0 Regards, Matt > no implementation for interface method > MonoDevelop.Ide.Codons.IDisplayBinding::get_DisplayName() in class > MonoDevelop.XmlEditor.XmlDisplayBinding > METHOD .ctor() > METHOD CanCreateContentForMimeType(string) > METHOD CreateContentForMimeType(string,System.IO.Stream) > METHOD CanCreateContentForFile(string) > METHOD CreateContentForFile(string)

Loading Comments...