Skip to content
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.

Segfault of unknown cause #39

Closed
seirl opened this issue Jan 24, 2015 · 2 comments
Closed

Segfault of unknown cause #39

seirl opened this issue Jan 24, 2015 · 2 comments
Labels

Comments

@seirl
Copy link

seirl commented Jan 24, 2015

This segfault happens quite regularly, still don't understand in what circumstances exactly.
I'm using bitlbee with libpurple.

#0  alarm_query () at tgl/queries.c:110
110     q->msg_id = tglmp_encrypt_send_message (TLS, q->session->c, q->data, q->data_len, (q->flags & QUERY_FORCE_SEND) | 1);
(gdb) bt
#0  alarm_query () at tgl/queries.c:110
#1  0x00007fce8d960221 in timer_alarm () from /usr/lib/purple-2/telegram-purple.so
#2  0x00007fcea0ac3eeb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcea0ac3355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fcea0ac3688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fcea0ac3a82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fcea16afd93 in main ()
@majn
Copy link
Owner

majn commented Jan 25, 2015

I think it may be a bug in libtgl, some timers arent removed when the connection is freed, and once the timers are called it crashes. Ive already submitted a pull request.

@majn majn added the bug label Jan 25, 2015
@majn
Copy link
Owner

majn commented Jan 30, 2015

I've pointed the current version of the repo to my tgl pull request, which fixes this issue.

If you pull, please make sure that all submodules are correctly synchronised and updated, easiest is to just clone a fresh version of this repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants