linuxdcpp-team team mailing list archive

[Fredrik <fredrik.strandin@xxxxxxxxx>]

Ok, I sat at another place with VNC at the previous post, so here comes
more:

[...]
BufferedSocket::connect() 0xafcc6a88
[New Thread 0xafaffb90 (LWP 1923)]
BufferedSocket::run() start 0xafcc6a88
threadConnect [IP-adress goes here]:1425
ConnectionManager::onMyNick 0xafb7a248, [DC nick goes here]
ConnectionManager::addUploadConnection, leaving to uploadmanager
Starting threadSend

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0xafaffb90 (LWP 1923)]
0xb7f1b424 in __kernel_vsyscall ()
(gdb) 

This is from just before the crash. The DC-nick and IP-adress (censored)
are the same for the previous 2 crashes. And when there is traffic
between me and him, I find more:

[...]
UnZFilter end, 128/122 = 1.0492
BufferedSocket::connect() 0xab1460b8
[New Thread 0xaddfdb90 (LWP 1753)]
BufferedSocket::run() start 0xab1460b8
threadConnect [IP-adress]:1425
ConnectionManager::onMyNick 0xaae03f98, [DC nick]
ConnectionManager::addUploadConnection, leaving to uploadmanager
Starting threadSend
Dynamically disabled compressionThrown: SocketException: Connection closed
UM::onFailed: Removing upload
ZFilter end, 393216/425984 = 0.9231
BufferedSocket: New command when already failed: 1
BufferedSocket::run() end 0xab1460b8
[Thread 0xaddfdb90 (LWP 1753) exited]
UnZFilter end, 208/176 = 1.1818
[...]

I hope this will help you out :)

P.S. I'm trying to PM the guy so I can find out his client D.S.

-- 
Crashes with segmentation fault
https://bugs.launchpad.net/bugs/555594
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.

Status in Linux DC++: New

Bug description:
When running linuxdcpp, it crashes with segmentation fault. Normally it takes over an hour between the start and crash, and within a day. But I have had periods where it worked for a week. (This means hashing, downloading, seeding etc. all works fine, until the crash).

I have newer succeeded to find out what the program is doing when it crashes, because I don't sit by the computer (server) all time.

I run Debian 5.0 i686, and compiled linuxdcpp 1.0.3 myself, guided by the manual. I had the same problem with 1.0.2.

An interesting thing was, that when running in gdb, the gui was still alive, but frozen, after the crash, while the whole program crashed at once when running linuxdcpp by it's own.