|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
SIGSEGV in gconfI'm getting these hard mono crashes. I really cannot explain them.
It crashes before it ever starts loading my addin. I reran my build of tomboy about 10 minutes after this and it worked fine. There have been a couple other reports of this on the mailing list ... any ideas? I'm running a pristine Ubuntu Juanty inside a VM. michaelfletcher@michaelfletcher-desktop:~/Desktop/tomboy-inst$ ./bin/tomboy (/home/michaelfletcher/Desktop/tomboy-inst/lib/tomboy/Tomboy.exe:7818): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.20.1/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function (/home/michaelfletcher/Desktop/tomboy-inst/lib/tomboy/Tomboy.exe:7818): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (/home/michaelfletcher/Desktop/tomboy-inst/lib/tomboy/Tomboy.exe:7818): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Stacktrace: at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0x00004> at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0xffffffff> at GConf.Client..ctor () <0x0003a> at Tomboy.GConfPreferencesClient..ctor () <0x0001d> at Tomboy.GnomeFactory.CreatePreferencesClient () <0x00016> at Tomboy.Services..cctor () <0x0004e> at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> at Tomboy.Application.Initialize (string,string,string,string[]) <0xffffffff> at Tomboy.Application.Initialize (string,string,string,string[]) <0x0000f> at Tomboy.Tomboy.Main (string[]) <0x00078> at (wrapper runtime-invoke) Tomboy.Tomboy.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xffffffff> Native stacktrace: mono [0x806d944] mono [0x808616b] [0xb7f90410] /usr/lib/libgconf-2.so.4(gconf_client_get_default+0xf8) [0xb6e8fa98] [0xb78898a8] [0xb7889753] [0xb78896d6] [0xb788969f] [0xb78884cf] [0xb788323e] mono [0x80be75d] mono(mono_runtime_class_init+0x19) [0x80bee19] mono [0x81b1d6e] mono [0x807029f] [0xb7ba1066] [0xb7883351] [0xb78831b3] mono(mono_runtime_exec_main+0xe5) [0x80bad75] mono(mono_runtime_run_main+0x16b) [0x80bb4eb] mono(mono_main+0x1727) [0x805c917] mono [0x805ac62] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d27775] mono [0x805aba1] Debug info from gdb: (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7cdd6e0 (LWP 7818)] [New Thread 0xb74ddb90 (LWP 7820)] [New Thread 0xb78dab90 (LWP 7819)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f90422 in __kernel_vsyscall () 3 Thread 0xb78dab90 (LWP 7819) 0xb7f90422 in __kernel_vsyscall () 2 Thread 0xb74ddb90 (LWP 7820) 0xb7f90422 in __kernel_vsyscall () 1 Thread 0xb7cdd6e0 (LWP 7818) 0xb7f90422 in __kernel_vsyscall () Thread 3 (Thread 0xb78dab90 (LWP 7819)): #0 0xb7f90422 in __kernel_vsyscall () #1 0xb7ea78f6 in nanosleep () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x081492e8 in ?? () #3 0xb7ea04ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #4 0xb7df549e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb74ddb90 (LWP 7820)): #0 0xb7f90422 in __kernel_vsyscall () #1 0xb7ea40e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0814c607 in ?? () #3 0x0814f1f4 in ?? () #4 0x0814f25c in ?? () #5 0x08169b02 in ?? () #6 0x080d565a in ?? () #7 0x080f7639 in ?? () #8 0x081653b6 in ?? () #9 0x081833b5 in ?? () #10 0xb7ea04ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #11 0xb7df549e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb7cdd6e0 (LWP 7818)): #0 0xb7f90422 in __kernel_vsyscall () #1 0xb7ea70fb in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0806da5e in ?? () #3 0x0808616b in ?? () #4 <signal handler called> #5 0xb6e8bff3 in ?? () from /usr/lib/libgconf-2.so.4 #6 0xb6e8fa98 in gconf_client_get_default () from /usr/lib/libgconf-2.so.4 #7 0xb78898a8 in ?? () #8 0xb7889753 in ?? () #9 0xb78896d6 in ?? () #10 0xb788969f in ?? () #11 0xb78884cf in ?? () #12 0xb788323e in ?? () #13 0x080be75d in ?? () #14 0x080bee19 in mono_runtime_class_init () #15 0x081b1d6e in ?? () #16 0x0807029f in ?? () #17 0xb7ba1066 in ?? () #18 0xb7883351 in ?? () #19 0xb78831b3 in ?? () #20 0x080bad75 in mono_runtime_exec_main () #21 0x080bb4eb in mono_runtime_run_main () #22 0x0805c917 in mono_main () #23 0x0805ac62 in ?? () #24 0xb7d27775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #25 0x0805aba1 in ?? () #0 0xb7f90422 in __kernel_vsyscall () ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Aborted _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: SIGSEGV in gconfOn Fri, Apr 24, 2009 at 7:48 PM, Michael Fletcher
<m.fletcher@...> wrote: > I'm getting these hard mono crashes. I really cannot explain them. > It crashes before it ever starts loading my addin. > > I reran my build of tomboy about 10 minutes after this and it worked fine. > > There have been a couple other reports of this on the mailing list ... > any ideas? > > I'm running a pristine Ubuntu Juanty inside a VM. Not happy to see this bug happening to more people. Could be a bug in gconf-sharp, downloading Jaunty to do some testing myself. For people who are experiencing this: are you 32-bit or 64-bit? Thanks, Sandy _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: SIGSEGV in gconf32 bit inside of the very latest sun VirtualBox. Its pretty much vanilla.
On Sat, Apr 25, 2009 at 7:16 AM, Sandy Armstrong <sanfordarmstrong@...> wrote: > On Fri, Apr 24, 2009 at 7:48 PM, Michael Fletcher > <m.fletcher@...> wrote: >> I'm getting these hard mono crashes. I really cannot explain them. >> It crashes before it ever starts loading my addin. >> >> I reran my build of tomboy about 10 minutes after this and it worked fine. >> >> There have been a couple other reports of this on the mailing list ... >> any ideas? >> >> I'm running a pristine Ubuntu Juanty inside a VM. > > Not happy to see this bug happening to more people. Could be a bug in > gconf-sharp, downloading Jaunty to do some testing myself. > > For people who are experiencing this: are you 32-bit or 64-bit? > > Thanks, > Sandy > > Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: SIGSEGV in gconfOn Fri, Apr 24, 2009 at 7:48 PM, Michael Fletcher
<m.fletcher@...> wrote: > I'm getting these hard mono crashes. I really cannot explain them. > It crashes before it ever starts loading my addin. > > I reran my build of tomboy about 10 minutes after this and it worked fine. > > There have been a couple other reports of this on the mailing list ... > any ideas? > > I'm running a pristine Ubuntu Juanty inside a VM. Oh, by the way, you really shouldn't be running Tomboy uninstalled if you're testing add-ins. Running uninstalled still uses your installed add-ins, when it should use your uninstalled add-ins [1]. And if you *do* want to run uninstalled, the proper way is to use `make run`. If you are *only* testing your add-in, you could just build and copy the addin DLL to ~/.tomboy/addins , then restart Tomboy. Installing Jaunty in a VM now. Sandy [1] http://bugzilla.gnome.org/show_bug.cgi?id=431833 _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: SIGSEGV in gconfI'm running 64 bit Arch Linux.
I'm getting the crashes often (2-3 times per day) but not consistently. I haven't been able to pin down the problem. > On Fri, Apr 24, 2009 at 7:48 PM, Michael Fletcher > <m.fletcher@...> wrote: >> I'm getting these hard mono crashes. I really cannot explain >> them. It crashes before it ever starts loading my addin. >> >> I reran my build of tomboy about 10 minutes after this and it >> worked fine. >> >> There have been a couple other reports of this on the mailing >> list ... any ideas? >> >> I'm running a pristine Ubuntu Juanty inside a VM. >> > Not happy to see this bug happening to more people. Could be a bug > in gconf-sharp, downloading Jaunty to do some testing myself. > > For people who are experiencing this: are you 32-bit or 64-bit? > > Thanks, > Sandy > _______________________________________________ > Tomboy-list mailing list > Tomboy-list@... > http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list- > beatniksoftware.com Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: SIGSEGV in gconfCharlie, you only get the crash when starting Tomboy, right? Not when
it's already been running for awhile? Thanks, Sandy On Sat, Apr 25, 2009 at 8:40 AM, Charlie Law <chaslaw@...> wrote: > I'm running 64 bit Arch Linux. > > I'm getting the crashes often (2-3 times per day) but not consistently. I haven't been able to pin down the problem. > >> On Fri, Apr 24, 2009 at 7:48 PM, Michael Fletcher >> <m.fletcher@...> wrote: >>> I'm getting these hard mono crashes. I really cannot explain >>> them. It crashes before it ever starts loading my addin. >>> >>> I reran my build of tomboy about 10 minutes after this and it >>> worked fine. >>> >>> There have been a couple other reports of this on the mailing >>> list ... any ideas? >>> >>> I'm running a pristine Ubuntu Juanty inside a VM. >>> >> Not happy to see this bug happening to more people. Could be a bug >> in gconf-sharp, downloading Jaunty to do some testing myself. >> >> For people who are experiencing this: are you 32-bit or 64-bit? >> >> Thanks, >> Sandy >> _______________________________________________ >> Tomboy-list mailing list >> Tomboy-list@... >> http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list- >> beatniksoftware.com > Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
| Free embeddable forum powered by Nabble | Forum Help |