Description
So, I made the mistake of upgrading ATS from trunk, without upgrading configs. And shit went to hell, with all the cores filling up my disk . I know, it's my mistake, but perhaps there's something we can do to at least not segfault when someone has the old configs? Not a huge deal, but I'd hate for a prod box to run into this.
The stack trace is below, if it makes any sense to you.
– Leif
#0 0x4006e045 in SSL_CTX_callback_ctrl () from /home/server/lib/libssl.so.1.0.0
#1 0x001dc2c0 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#2 0x0828c843 in SSLNetVConnection::sslStartHandShake (this=0xb52d230, event=0, err=@0x411f2e60) at SSLNetVConnection.cc:501
#3 0x0828e1b0 in SSLNetVConnection::net_read_io (this=0xb52d230, nh=0xac250d0, lthread=0xac22000) at SSLNetVConnection.cc:251
#4 0x0829589e in NetHandler::mainNetEvent (this=0xac250d0, event=5, e=0x9eb5980) at UnixNet.cc:372
#5 0x082c3774 in EThread::process_event (this=0xac22000, e=0x9eb5980, calling_code=5) at I_Continuation.h:146
#6 0x082c3f7e in EThread::execute (this=0xac22000) at UnixEThread.cc:264
#7 0x082c2b31 in spawn_thread_internal (a=0x9a6da80) at Thread.cc:88
#8 0x0037544b in start_thread () from /lib/libpthread.so.0
#9 0x002b880e in clone () from /lib/libc.so.6