Package: monodevelop
State: installed
Automatically installed: yes
Version: 0.14+dfsg-3

On load, monodevelop crashes when the TMPDIR environment variable
references an invalid directory. The crash details are included below. 

I found this when I had the same error as reported in bug #430570:
Monodevelop crashes on opening solution
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430570)

I was trying to figure out what was going on and, even after removing
all project files in the system so that everything was clean the system
continued to crash.

I then purged all mono-related files, followed by installing monodevelop
alone with its dependencies. monodevelop continued to crash on load with
the error shown below.

I'm not sure if the errors I received that matched bug #430570 may have
had the same cause as this error and just expressed it differently or
not.

In any case, removing TMPDIR from the environment resolved the issue and
monodevelop now loads.

Hope this helps.

Eric

[New Thread 0xb737eb90 (LWP 30340)]
[New Thread 0xb7f98b90 (LWP 30339)]
0xffffe410 in __kernel_vsyscall ()
  3 Thread 0xb7f98b90 (LWP 30339)  0xffffe410 in __kernel_vsyscall ()
  2 Thread 0xb737eb90 (LWP 30340)  0xffffe410 in __kernel_vsyscall ()
  1 Thread 0xb7d2f6d0 (LWP 30331)  0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb7f98b90 (LWP 30339)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ed6196 in nanosleep () from /lib/i686/cmov/libpthread.so.0
#2  0x08133c17 in ?? ()
#3  0xb7f983ac in ?? ()
#4  0x00000000 in ?? ()

Thread 2 (Thread 0xb737eb90 (LWP 30340)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ed2aa5 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0x08138b74 in ?? ()
#3  0xb78581dc in ?? ()
#4  0xb78581c4 in ?? ()
#5  0xb737e198 in ?? ()
#6  0x00007684 in ?? ()
#7  0x08137b20 in ?? ()
#8  0x00000006 in ?? ()
#9  0xb737e1c8 in ?? ()
#10 0x0814ab35 in ?? ()
#11 0x00000404 in ?? ()
#12 0x0824d364 in ?? ()
#13 0xb737e1d8 in ?? ()
#14 0x08138e81 in ?? ()
#15 0xb78581dc in ?? ()
#16 0xb78581c4 in ?? ()
#17 0x00000000 in ?? ()

Thread 1 (Thread 0xb7d2f6d0 (LWP 30331)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e26021 in select () from /lib/i686/cmov/libc.so.6
#2  0xb7f455f4 in IA__g_spawn_sync (working_directory=0x0,
argv=0x86b9398, 
    envp=0x0, flags=<value optimized out>, child_setup=0,
user_data=0x0, 
    standard_output=0xbfdf74e4, standard_error=0xbfdf74e0, 
    exit_status=0xbfdf74dc, error=0x0)
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c:300
#3  0xb7f459bc in IA__g_spawn_command_line_sync (
    command_line=0xbfdf6cdc "gdb --ex 'attach 30331' --ex 'info threads'
--ex 'thread apply all bt' --batch", standard_output=0xbfdf74e4, 
    standard_error=0xbfdf74e0, exit_status=0xbfdf74dc, error=0x0)
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c:677
#4  0x081ab53b in ?? ()
#5  0xbfdf6cdc in ?? ()
#6  0xbfdf74e4 in ?? ()
#7  0xbfdf74e0 in ?? ()
#8  0xbfdf74dc in ?? ()
#9  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()


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

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to