Bug#710696: severity of 710696 is serious, because it's a FTBFS bug

[Santiago Vila]

On Thu, Sep 29, 2016 at 04:46:04PM +0200, Michael Biebl wrote:

> Can you get us a proper backtrace of such a crash. It should be possible
> to only run tests/multipart-test in gdb

I get this:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/build/libsoup2.4-2.56.0/tests/.libs/lt-multipart-test -k --tap'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f7dc9f77005 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Current thread is 1 (Thread 0x7f7dcaedd880 (LWP 30184))]
(gdb) bt
#0  0x00007f7dc9f77005 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f7dc9f2eb50 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f7dca860778 in soup_session_dispose (object=0x55accb44e110)
    at soup-session.c:317
#3  0x00007f7dca20ec05 in g_object_unref ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x000055acca1545e9 in main (argc=<optimized out>, argv=<optimized out>)
    at multipart-test.c:515

but I don't think it has more information than the backtrace you already posted in bugzilla.

Thanks.