#14 Segfault accepting key on newly created account

closed-fixed
None
5
2003-08-10
2003-07-31
wabu
No

I've managed to find a reproducable segfault, although
rather obscure (not something you are likely to do often).

It occurs when you accept keys talking to someone new
on an newly created account in the same gaim session.
(IE, create an account, talk to someone via that
account, dont close gaim at any point).

Reproducable: Always

Steps to reproduce:
(First few steps to remove keys so you are setup right
for the conditions)
1) Run gaim
2) Unload gaim-encryption plugin
3) If you have an account to spare, remove it.
4) Close gaim
5) Delete (or move somewhere else for safe keeping)
.gaim/id .gaim/id.priv .gaim/encrypt.prefs
(At this point you'll be in the right conditions)
6) Run gaim
7) Create a new account
8) Connect to the account
9) Talk to someone encrypted
10) A dialog box pops up "Gaim-Encryption Key Received".
11) Click "Accept and Save"
12) Segfault

Here is the gdb backtrace (I hope this is useful, I
followed the gaim debugging page):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3923)]
0x40390e20 in strnlen () from /lib/libc.so.6
(gdb) bt
#0 0x40390e20 in strnlen () from /lib/libc.so.6
#1 0x403613b8 in vfprintf () from /lib/libc.so.6
#2 0x4037c70c in vsprintf () from /lib/libc.so.6
#3 0x4036967d in sprintf () from /lib/libc.so.6
#4 0x40c31c55 in GE_send_msg () from
/usr/lib/gaim/encrypt.so
#5 0x40c310d7 in GE_send_stored_msgs () from
/usr/lib/gaim/encrypt.so
#6 0x40c366a2 in save_key_callback () from
/usr/lib/gaim/encrypt.so
#7 0x4073e42f in g_cclosure_marshal_VOID__VOID ()
from /usr/lib/libgobject-2.0.so.0
#8 0x4072be23 in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#9 0x4073e03f in signal_emit_unlocked_R () from
/usr/lib/libgobject-2.0.so.0
#10 0x4073d058 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#11 0x4073d2ac in g_signal_emit () from
/usr/lib/libgobject-2.0.so.0
#12 0x40497515 in gtk_button_clicked () from
/usr/lib/libgtk-x11-2.0.so.0
#13 0x404980fb in gtk_real_button_released () from
/usr/lib/libgtk-x11-2.0.so.0
#14 0x4073e42f in g_cclosure_marshal_VOID__VOID ()
from /usr/lib/libgobject-2.0.so.0
#15 0x4072c46f in g_type_class_meta_marshal ()
from /usr/lib/libgobject-2.0.so.0
#16 0x4072be23 in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#17 0x4073d8d0 in signal_emit_unlocked_R () from
/usr/lib/libgobject-2.0.so.0
#18 0x4073d058 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#19 0x4073d2ac in g_signal_emit () from
/usr/lib/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#20 0x404974dd in gtk_button_released () from
/usr/lib/libgtk-x11-2.0.so.0
#21 0x40497f8c in gtk_button_button_release ()
from /usr/lib/libgtk-x11-2.0.so.0
#22 0x40501fde in _gtk_marshal_BOOLEAN__BOXED ()
from /usr/lib/libgtk-x11-2.0.so.0
#23 0x4072c46f in g_type_class_meta_marshal ()
from /usr/lib/libgobject-2.0.so.0
#24 0x4072be23 in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#25 0x4073dafa in signal_emit_unlocked_R () from
/usr/lib/libgobject-2.0.so.0
#26 0x4073cdd8 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#27 0x4073d2ac in g_signal_emit () from
/usr/lib/libgobject-2.0.so.0
#28 0x405a9c6b in gtk_widget_event_internal ()
from /usr/lib/libgtk-x11-2.0.so.0
#29 0x40501e67 in gtk_propagate_event () from
/usr/lib/libgtk-x11-2.0.so.0
#30 0x40500f18 in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
#31 0x406525e1 in gdk_event_dispatch () from
/usr/lib/libgdk-x11-2.0.so.0
#32 0x40786190 in g_main_dispatch () from
/usr/lib/libglib-2.0.so.0
#33 0x40784608 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#34 0x4078664b in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#35 0x40784bef in g_main_loop_run () from
/usr/lib/libglib-2.0.so.0
#36 0x405007cf in gtk_main () from
/usr/lib/libgtk-x11-2.0.so.0
#37 0x080e8c4d in main ()
#38 0x4032ba87 in __libc_start_main () from /lib/libc.so.6

Discussion

  • Bill Tompkins

    Bill Tompkins - 2003-07-31
    • assigned_to: nobody --> obobo
    • status: open --> open-duplicate
     
  • Bill Tompkins

    Bill Tompkins - 2003-07-31

    Logged In: YES
    user_id=21203

    Yep, this is the same as bug 780290. Should be
    straightforward to track down and fix in the next release.

     
  • Bill Tompkins

    Bill Tompkins - 2003-08-10
    • status: open-duplicate --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks