[sylpheed:36759] Re: Strange bug with small screen

[Stefan Vorkoetter]

Just to keep everyone in the loop, here's what I've discovered when running a debug version of sylpheed and attaching a debugger to it.


Case 1: Clicking "Compose":

Program received signal SIGSEGV, Segmentation fault.
0x0007b170 in compose_update_signature_menu (compose=0x20fcb80)
    at compose.c:3027
3027                        compose->account->sig_names[i][0] != '\0') {

(gdb) where
#0  0x0007b170 in compose_update_signature_menu (compose=0x20fcb80)
    at compose.c:3027
#1  0x0007b058 in compose_select_account (compose=0x20fcb80,
    account=0x20ace70, init=1) at compose.c:3002
#2  0x000841c4 in compose_create (account=0x20ace70, mode=COMPOSE_NEW)
    at compose.c:5886
#3  0x00074ea4 in compose_new (account=0x20ace70, item=0x21563a0, mailto=0x0,
    attach_files=0x0) at compose.c:772
#4  0x0003d80c in compose_cb (mainwin=0x1e0b510, action=0, widget=0x0)
    at mainwindow.c:3643
#5  0x0003b680 in toolbar_compose_cb (widget=0x20331f0, data=0x1e0b510)
    at mainwindow.c:2880
#6  0x76509afc in ?? () from /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0

(gdb) print compose->account->sig_names
$13 = {0x0, 0x29 <error: Cannot access memory at address 0x29>, 0x20479f0 "",
  0x7650e3c4 <g_object_ref> "8 at -\351P\020\240", <incomplete sequence \343>,
  0x20479f0 "",
  0x7650e650 <g_object_unref> "\370C-\351P\020\240", <incomplete sequence \343>, 0x20479f0 "", 0x76513524 "p@", <incomplete sequence \351>,
  0x2092828 "`t\374\001\002",
  0x7651bbd4 "\b3\237\345\bß\345\003\060\217\340\360O", <incomplete sequence \351>}
  

Case 2: Clicking "Preferences for Current Account" on the "Configuration menu:

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../ports/sysdeps/arm/armv6/strlen.S:26
26      ../ports/sysdeps/arm/armv6/strlen.S: No such file or directory.

(gdb) where
#0  strlen () at ../ports/sysdeps/arm/armv6/strlen.S:26
#1  0x762d461c in g_strdup () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
#2  0x000aa138 in prefs_account_open (ac_prefs=0x146e768)
    at prefs_account_dialog.c:562
#3  0x000c2f20 in account_open (ac_prefs=0x146e768) at account_dialog.c:212
#4  0x0003e89c in prefs_account_open_cb (mainwin=0x1127510, action=0,
    widget=0x133cd60) at mainwindow.c:4048
#5  0x7648188c in g_closure_invoke ()
   from /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0

(gdb) up 2
#2  0x000aa138 in prefs_account_open (ac_prefs=0x146e768)
    at prefs_account_dialog.c:562
562                             compose.sig_names[i] = g_strdup(ac_prefs->sig_names[i]);

(gdb) print ac_prefs->sig_names
$2 = {0x0, 0x29 <error: Cannot access memory at address 0x29>,
  0x6d6f682f <error: Cannot access memory at address 0x6d6f682f>,
  0x76732f65 "",
  0x6f6b726f <error: Cannot access memory at address 0x6f6b726f>,
  0x65747465 <error: Cannot access memory at address 0x65747465>,
  0x732e2f72 <error: Cannot access memory at address 0x732e2f72>,
  0x616e6769 <error: Cannot access memory at address 0x616e6769>,
  0x65727574 <error: Cannot access memory at address 0x65727574>, 0x0}


In both cases, it's pointing to a problem with the signatures, namely that the sig_names array is corrupted. I will investigate further.

Stefan

-- 
Stefan Vorkoetter
http://www.stefanv.com