Bug 321640 (MONO78924) - Got SIGSEGV while executing native code
Summary: Got SIGSEGV while executing native code
Status: RESOLVED MOVED
Alias: MONO78924
Product: Mono: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: 1.0
Hardware: Other Other
: P3 - Medium : Critical
Target Milestone: ---
Assignee: Paolo Molaro
QA Contact: Mono Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-21 23:09 UTC by Ritvik Mayank
Modified: 2007-09-15 21:24 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiest 2007-09-15 20:04:23 UTC


---- Reported by mails.ritvik@gmail.com 2006-07-21 16:09:48 MST ----

Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
while running Tomboy got the following error message
Got SIGSEGV while executing native code

Steps to reproduce the problem:
1. install tomboy Version 0.3.5 
2. run tomboy --new-note 
3. write something
4. Clt + c
5. Stacktrace 

Actual Results:
rix@rix-sys:~$ tomboy --new-note
something

=================================================================
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.
=================================================================

Stacktrace:

in (wrapper managed-to-native) System.Threading.Monitor:Monitor_try_enter
(object,int) <0x4>
in (wrapper managed-to-native) System.Threading.Monitor:Monitor_try_enter
(object,int) <0xffffffb3>
in System.Threading.Monitor:Enter (object) <0x13>
in (wrapper synchronized) DBus.Service:remove_SignalCalled
(DBus.Service/SignalCalledHandler) <0xffffffe5>
in Tomboy.RemoteControlProxy.Proxy:Finalize () <0x15>
in (wrapper runtime-invoke) System.Object:runtime_invoke_void
(object,intptr,intptr,intptr) <0xddff27>

Native stacktrace:

        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xe3) [0xb7df043f]
        /usr/lib/libmono.so.0 [0xb7db203e]
        [0xffffe440]
       
/usr/lib/libmono.so.0(ves_icall_System_Threading_Monitor_Monitor_try_enter+0x2f)
[0xb7e60c7c]
        [0xb7006499]
        [0xb7006424]
        [0xb6fef5ec]
        [0xb6fef5be]
        [0xb6fef539]
        /usr/lib/libmono.so.0 [0xb7dcf438]
        /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0xb7e31eed]
        /usr/lib/libmono.so.0 [0xb7e4c09a]
        /usr/lib/libmono.so.0 [0xb7e4cd12]
        /usr/lib/libmono.so.0 [0xb7e63456]
        /usr/lib/libmono.so.0 [0xb7ead60f]
        /usr/lib/libmono.so.0(GC_start_routine+0x5f) [0xb7ec73b3]
        /lib/tls/i686/cmov/libpthread.so.0 [0xb7cc8341]
        /lib/tls/i686/cmov/libc.so.6(__clone+0x5e) [0xb7c324ee]
Aborted


Expected Results:
should run tomboy and create a new note

How often does this happen? 
Always 

Additional Information:
Mono JIT compiler version 1.1.13.6 
installed using apt-get along with Tomboy.



---- Additional Comments From dick@ximian.com 2006-07-24 12:42:30 MST ----

This is a dbus-sharp bug.  We thought it was fixed in dbus-sharp 0.60
but my fc5 machine with dbus-sharp 0.61 still shows the bug.

*** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO76843 ***


Unknown bug field "cf_op_sys_details" encountered while moving bug
   <cf_op_sys_details>Ubuntu 6.06 LTS (2.6.15-23-386)</cf_op_sys_details>
Unknown operating system unknown. Setting to default OS "Other".
This bug was marked DUPLICATE in the database it was moved from.
    Changing resolution to "MOVED"