This was actually sent automatically by Apport. Here is what I can find in the Apport log:
> ERROR: apport (pid 6194) Tue Apr 16 20:29:04 2013: called for pid 5969, > signal > 6, core limit 0 > ERROR: apport (pid 6194) Tue Apr 16 20:29:04 2013: executable: > /usr/bin/xbrlapi (command line "/usr/bin/xbrlapi -q") > ERROR: apport (pid 6194) Tue Apr 16 20:29:04 2013: is_closing_session(): no > DBUS_SESSION_BUS_ADDRESS in environment > ERROR: apport (pid 6194) Tue Apr 16 20:29:04 2013: this executable already > crashed 2 times, ignoring This occurred two additional times, with only the PID differing. All brlapi entries in other logs appear normal. -----Original Message----- From: Samuel Thibault <sthiba...@debian.org> To: whrav...@gmail.com, 705...@bugs.debian.org Subject: Re: Bug#705434: xbrlapi crashed with SIGABRT in brlapi__defaultExceptionHandler() Date: Tue, 16 Apr 2013 23:59:29 +0200 Hello, whrav...@gmail.com, le Mon 15 Apr 2013 01:36:26 +0200, a écrit : > #2 0x00007fe79c31808a in brlapi__defaultExceptionHandler () from > /lib/x86_64-linux-gnu/libbrlapi.so.0.5 > No symbol table info available. Do you have the error log from xbrlapi? Only the backtrace does not provide much information about what happened. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
