bogged down

bug's picture

I’ve been running into memory violations that GDB can’t backtrace for me (more than just SIGSEGV, that is), so valgrind is the tool of choice for now. Since testing requires a public server, I have the choice of either punching holes in my firewall to test locally, or to run on an already public remote machine. The server I’ve been testing on doesn’t have valgrind, though, so I tried getting BZFS to run on my personal VPS. I probably spent a bit too much time on this, although at several points it looked like it would be simple. Eventually, Thumper helped out by running valgrind on my code from his own server and giving me the output, with which I was able to find a few bugs. Thursday will continue the hunt, so Friday might finally be the start of semantic testing.

Comments

valgrind on bzflag.bz

brlcad has valgrind installed on bzflag.bz (not the .de box)