Re: Beagle-extract-content runtime error

> ... As a result, I was
> able to run a larger scale experiment using beagle-extract-content and
> now seem to have run into an error from beagle-extract-content
> (doesn't seem like a mono error). The backtrace output is supplied
...
> ** (/usr/lib/beagle/ExtractContent.exe:8082): WARNING **:
> _wapi_thread_abandon_mutexes: error looking up threa
> d handle 0x408
>
> ** (/usr/lib/beagle/ExtractContent.exe:8082): WARNING **:
> _wapi_thread_set_termination_details: error looking
> up thread handle 0x408
> *** glibc detected *** beagle-extract-content: double free or
> corruption (out): 0x00000000007154c0 ***
> ======= Backtrace: =========
> /lib/libc.so.6[0x2b606c09ab23]
> /lib/libc.so.6(cfree+0x8c)[0x2b606c09e26c]
> /usr/lib/libglib-2.0.so.0(g_ptr_array_free+0x4a)[0x2b606b4ebc6a]
> beagle-extract-content[0x4d1e8c]
> beagle-extract-content(mono_thread_cleanup+0x10)[0x488900]
> beagle-extract-content(mono_runtime_cleanup+0x18)[0x493f88]
> beagle-extract-content[0x4e978a]
> beagle-extract-content(mono_main+0x1152)[0x416112]
> /lib/libc.so.6(__libc_start_main+0xf4)[0x2b606c0488e4]
> beagle-extract-content(fmod+0x72)[0x414a3a]
...

Unfortunately its mono again :-(. By staring at it, it seems that mono is 
failing miserably when multiple instances of the same process are running. 
Should be an interesting test case for the mono folks.

- dBera

-- 
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE / Mandriva / Inspiron-1100