[ubuntu-mono] [Bug 230306] Re: update the hardy version to the new 0.4.3.1?

matteo matteo.turilli at oerc.ox.ac.uk
Wed Jun 4 17:21:17 UTC 2008


Not sure this is the right place where to post. Apologies if not.

f-spot 0.4.3.1-0ubuntu1 aborts on AMD64

Here the error and debug:

TYPE: 1
**
** ERROR:(mini-amd64.c:192):amd64_patch: assertion failed: (amd64_is_imm32 (disp))
Stacktrace:


Native stacktrace:

	f-spot [0x51bb67]
	/lib/libpthread.so.0 [0x7f08b58ce7d0]
	/lib/libc.so.6(gsignal+0x35) [0x7f08b530f095]
	/lib/libc.so.6(abort+0x110) [0x7f08b5310af0]
	/usr/lib/libglib-2.0.so.0(g_assertion_message+0x117) [0x7f08b5d39bc7]
	/usr/lib/libglib-2.0.so.0 [0x7f08b5d3a062]
	f-spot [0x42dbb8]
	f-spot [0x4e6229]
	f-spot [0x50849b]
	f-spot [0x508cd9]
	f-spot [0x5091d3]
	f-spot(mono_exception_from_name_two_strings+0xdd) [0x48c38d]
	f-spot(mono_runtime_init+0x13e) [0x48e64e]
	f-spot [0x4e31e5]
	f-spot(mono_main+0x341) [0x4169b1]
	/lib/libc.so.6(__libc_start_main+0xf4) [0x7f08b52fb1c4]
	f-spot(realloc+0x381) [0x416109]

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 0x7f08b65ae7a0 (LWP 23364)]
[New Thread 0x7f08b6429950 (LWP 23365)]
(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)
0x00007f08b53adda2 in select () from /lib/libc.so.6
  2 Thread 0x7f08b6429950 (LWP 23365)  0x00007f08b58cde81 in nanosleep ()
   from /lib/libpthread.so.0
  1 Thread 0x7f08b65ae7a0 (LWP 23364)  0x00007f08b53adda2 in select ()
   from /lib/libc.so.6

Thread 2 (Thread 0x7f08b6429950 (LWP 23365)):
#0  0x00007f08b58cde81 in nanosleep () from /lib/libpthread.so.0
#1  0x00000000004b8f4f in ?? ()
#2  0x00007f08b58c63f7 in start_thread () from /lib/libpthread.so.0
#3  0x00007f08b53b4b2d in clone () from /lib/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f08b65ae7a0 (LWP 23364)):
#0  0x00007f08b53adda2 in select () from /lib/libc.so.6
#1  0x00007f08b5d4a9bc in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#2  0x00007f08b5d4ad98 in g_spawn_command_line_sync ()
   from /usr/lib/libglib-2.0.so.0
#3  0x000000000051bbf9 in ?? ()
#4  <signal handler called>
#5  0x00007f08b530f095 in raise () from /lib/libc.so.6
#6  0x00007f08b5310af0 in abort () from /lib/libc.so.6
#7  0x00007f08b5d39bc7 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#8  0x00007f08b5d3a062 in g_assertion_message_expr ()
   from /usr/lib/libglib-2.0.so.0
#9  0x000000000042dbb8 in ?? ()
#10 0x00000000004e6229 in ?? ()
#11 0x000000000050849b in ?? ()
#12 0x0000000000508cd9 in ?? ()
#13 0x00000000005091d3 in ?? ()
#14 0x000000000048c38d in mono_exception_from_name_two_strings ()
#15 0x000000000048e64e in mono_runtime_init ()
#16 0x00000000004e31e5 in ?? ()
#17 0x00000000004169b1 in mono_main ()
#18 0x00007f08b52fb1c4 in __libc_start_main () from /lib/libc.so.6
#19 0x0000000000416109 in ?? ()
#20 0x00007fffbe5c8ae8 in ?? ()
#21 0x0000000000000000 in ?? ()
#0  0x00007f08b53adda2 in select () from /lib/libc.so.6


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

Aborted

-- 
update the hardy version to the new 0.4.3.1?
https://bugs.launchpad.net/bugs/230306
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.




More information about the Ubuntu-mono mailing list