Re: Bitcoind

debug.log attached

That narrows it down a lot. It didn’t print any IRC activity in debug.log, so I guess it couldn’t have gotten past the RecvUntil. Eyeballing it I don’t see anything obvious. I guess it would have to be either in ConnectSocket or RecvUntil.

Try it with the attached irc.cpp and net.cpp and send me the debug.log.

Or you could run it in gdb and step through ThreadIRCSeed gdb —args bitcoin [switches] b ThreadIRCSeed run step or u to step over and up out of routines.

Quote from: mmalmi@cc.hut.fi on March 03, 2010, 1:50:39 AM UTC

I get the error regardless of the getinfo. Commenting out
ThreadIRCSeed fixed the problem.

Quote from: Satoshi Nakamoto on March 02, 2010, 10:27:22 PM UTC

Does it still do it if you didn’t do getinfo?

You could comment out the CreateThreads listed below, then re-enable them one at a time until it does it again. Then we would know which thread the problem is in.

net.cpp, under // Start threads CreateThread(ThreadIRCSeed, NULL) CreateThread(ThreadSocketHandler, NULL, true) CreateThread(ThreadOpenConnections, NULL) CreateThread(ThreadMessageHandler, NULL)

init.cpp: CreateThread(ThreadRPCServer, NULL);

Quote from: mmalmi@cc.hut.fi on March 02, 2010, 7:36:10 PM UTC

Here goes. I forgot to mention the crash error message:

terminate called after throwing an instance of ‘std::bad_alloc’ what(): std::bad_alloc

Quote from: Satoshi Nakamoto on February 28, 2010, 8:09:07 PM UTC

Could you send me the debug.log?

Quote from: mmalmi@cc.hut.fi on February 28, 2010, 4:12:44 AM UTC

I tried debugging my build of bitcoind with ddd debugger, but
didn’t have much success yet. It always ends up taking all the
system’s memory and finally crashes. Could you please send
me again the latest 64 bit build of bitcoind, so I can see
if the problem is about my build?