RE: silc-client segfault when using /quit or disconnect
Skywing <[email protected]> Thu, 6 Nov 2008 09:32:33 -0600
| Newsgroups | gmane.network.silc.devel |
|---|---|
| Message-ID | <982D8D05B6407A49AD506E6C3AC8E7D6BE3B8F0E8F@caralain.haven.nynaeve.net> |
I think that Pekka has integrated the necessary patch for this as of the latest release. Copying him to be certain, however. - S -----Original Message----- From: silc-devel-bounces-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected] [mailto:silc-devel-bounces-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected]] On Behalf Of Caspar Clemens Mierau Sent: Thursday, November 06, 2008 10:33 AM To: silc-devel-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected] Subject: silc-client segfault when using /quit or disconnect Hi there, let me introduce a bug from the launchpad bug tracker to you: https://bugs.launchpad.net/ubuntu/+source/silc-client/+bug/275989 It seems, that silc-client crashes when you are using "/key channel" protected channels and use /quit or get a disconnect. In order to reproduce it, try: - start silc session - connect to a server - join a channel that has a "/key channel CHANNELNAME password PASSWORD" set and set it - "/quit" silc-client will crash with a hint on "silccipher.c:377" when having debug symbols installed. it will also crash, when you have a forced disconnect (due to connectivity). You'll find a backtrace here: http://launchpadlibrarian.net/18055254/silc-gdb.txt I assume there needs to be a check like "if (!(channel->internal.send_key == NULL))" close to silccipher.c:377 this behaviour has been found on Ubuntu Hardy and Intrepid. Maybe a check against the newest release is necessary. I hope these information help investigating the bug. If you provide a patch, I'll send it to the Debian and Ubuntu project. Best. _______________________________________________________________________ Info: https://lists.silcnet.org/mailman/listinfo/silc-announce Archive: https://lists.silcnet.org/pipermail/silc-announce FAQ: http://silcnet.org/support/faq/