crash in g_io_channel_get_buffer_condition

Bug #402514 reported by Greg Hazel on 2009-05-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

(gdb) bt
#0 0xb7cdc1b6 in raise () from /lib/
#1 0xb7cdda31 in abort () from /lib/
#2 0x0805130d in signal_crash (sig=11) at src/main.c:101
#3 <signal handler called>
#4 0xb7e8d866 in g_io_channel_get_buffer_condition () from /usr/lib/
#5 0x0806a184 in transport_parse_buffer (transport=0x24cd0540) at lib/transport.c:369
#6 0x08058f7d in client_init_iochannel (n=0x80a2f50, c=0x22aee648,
    desc=0x23541520 "") at src/client.c:280
#7 0x080613a5 in handle_client_line (pc=0x238c5c68, l=0x254d2da0) at src/listener.c:252
#8 0x08070f39 in handle_client_receive (c=0x22aee648, condition=<value optimized out>,
    data=0x238c5c68) at lib/listener.c:249
#9 0xb7ecd0ed in ?? () from /usr/lib/
#10 0xb7e98dd6 in g_main_context_dispatch () from /usr/lib/
#11 0xb7e9c193 in ?? () from /usr/lib/
#12 0xb7e9c577 in g_main_loop_run () from /usr/lib/
#13 0x08050f99 in main (argc=Cannot access memory at address 0x1
) at src/main.c:384

Jelmer Vernooij (jelmer) on 2009-07-21
Changed in ctrlproxy:
status: New → Triaged
Jelmer Vernooij (jelmer) on 2010-09-09
Changed in ctrlproxy:
assignee: Jelmer Vernooij (jelmer) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers