Segfault after extended periods of client disconnect

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start dircproxy
2. Join a bunch of servers & channels
3. Disconnect the client from dircproxy
4. Wait for a few days
5. dircproxy process crashes

What is the expected output? What do you see instead?

I expect it not to crash :-)


What version of the product are you using? On what operating system?

I'm using 1.2b2 on Debian Lenny.


Please provide any additional information below.

When I used to disconnect every day to go to/from work, I would find that
dircproxy would crash like this about once /week.  Now that I disconnect
less frequently I find it can take perhaps three weeks.  The segfault never
happens when I am actually connected to dircproxy.

I started strace running on my last dircproxy session, to try and see if
anything useful can be got from the strace, which I logged to the system
debug log.  The last 3/4 hour of that log is in the attached file.

Original issue reported on code.google.com by andrew.m...@gmail.com on 4 Nov 2008 at 8:30

Attachments:

• dircproxy-crash.log

[GoogleCodeExporter]

maybe it was the random crash error before the current version, (ctcp related), 
it
should be ok now, but we need to test.

Original comment by francois...@gtempaccount.com on 27 Mar 2009 at 4:27

[GoogleCodeExporter]

OK, I'm cloning the current trunk now and will (try to) build that.  It will be 
weeks
until I have greater confidence the problem is solved though...

I'll try to disconnect every night in order to encourage the crash sooner :-)

Regards,
Andrew McMillan.

Original comment by andrew.m...@gmail.com on 27 Mar 2009 at 7:57