silc client segfaults when connecting to us.silcnet.org: gdb silc [it loads] /connect us.silcnet.org (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 32769 (LWP 16439)] [New Thread 16386 (LWP 16440)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 16429)] 0x402abf97 in free () from /lib/libc.so.6 (gdb) bt #0 0x402abf97 in free () from /lib/libc.so.6 #1 0x0810fbfb in silc_ske_payload_start_free () #2 0x0810c4ca in silc_ske_free () #3 0x080d4574 in silc_client_add_connection () #4 0x0811ad36 in silc_protocol_execute_final () #5 0x080efe77 in silc_client_protocols_unregister () #6 0x0811ad07 in silc_protocol_execute () #7 0x080efc4a in silc_client_protocols_unregister () #8 0x0811ad07 in silc_protocol_execute () #9 0x080d4f6a in silc_client_packet_process () #10 0x080d4df9 in silc_client_packet_process () #11 0x080f42d2 in silc_packet_receive_process () #12 0x080d4cd0 in silc_client_packet_process () #13 0x0811548b in silc_schedule_signal_call () #14 0x081144d4 in silc_schedule_one () #15 0x080d657c in silc_client_run_one () #16 0x0809d7f3 in silc_core_deinit () (gdb)
bumping the vesion to 0.9.10.1 fixes it...though I did have to build with FEATURES="-sandbox" to emerge the bumped version.
did you get any sandbox problems? or do you just usually use -sandbox ?
btw, 0.9.11 is out so please let us know if things have improved. it doesn't segv for me.
I don't usually use "-sandbox" as it is a usefull feature of portage. I haven't used slic for a bit, so now that there is a new version, I'll have to check it out. Does the ebuild use the new version?
any luck with the new version? its been in portage for a while now.
please reopen the problem still exists.
