[Box Backup] Failing tests

[Guno Heitman]

Chris Wilson wrote:
> 
> I suspect that what's happening is that the C++ objects are being 
> deallocated in a bad order, which causes the built-in memory leak tracking 
> to fail. To check this, please could you run the test under gdb (using the 
> t-gdb script in debug/test/bbackupd) and print a backtrace when it crashes 
> (bt command)?

The debug/test/bbackupd directory is empty here (Should I perhaps
checkout another branch instead of the trunk?). However, there is a
t-gdb script in release/test/bbackupd, and this gives the following output:

Program received signal SIGSEGV, Segmentation fault.
Timers::Cleanup () at
/usr/lib/gcc/i486-slackware-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_vector.h:752
752             this->_M_impl._M_finish = this->_M_impl._M_start;

When issuing the bt command, the output is similar:

(gdb) bt
#0  Timers::Cleanup ()
    at
/usr/lib/gcc/i486-slackware-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_vector.h:752
#1  0x0805fdd1 in main (argc=1, argv=0xbf8afe84) at _main.cpp:254

regards,

Guno