[Sugar-devel] debugging weird Activity startup errors

Daniel Drake dsd at laptop.org
Wed Aug 28 11:04:19 EDT 2013


On Tue, Aug 27, 2013 at 5:43 PM, Peter Robinson <pbrobinson at gmail.com> wrote:
> Hi All,
>
> I'm testing locally a scratch build of Abiword 3 with the intent of having
> it in Fedora for F-20 and hence SoaSv10 but I'm getting a near useless error
> in the Activity log of:
>
> Terminated by signal 11, pid 1142 data (None, <open file '<fdopen>', mode
> 'w' at 0x251bd20>, dbus.ByteArray('ef47d2e4dc6551ba96f6ceded9023243ea4ee519'
> , variant_level=1))

Signal 11 is a segmentation fault, i.e. a hard crash.

Run it in gdb with:

    sugar-launch -d org.laptop.AbiWordActivity

(not sure if I have the activity ID correct there)

When it crashes soon after, run "bt" at gdb prompt.

The output will give us some idea of what is going wrong.

Daniel


More information about the Sugar-devel mailing list