On 10/19/2011 10:10 AM, Phil Mayers wrote:
Ah ha - presumably that was why my 2.1.12 install ballooned it's RAM; it was nothing to do with 2.1.12, but the fact I'd enabled session resumption.
Oops; I applied the patch in c145c7dabbd48 to my 2.1.12 servers, and last night we had a segfault after running fine for several hours. I restarted under GDB and caught a backtrace: #0 paircopyvp (vp=0x101010101010101) at valuepair.c:327 n = <value optimized out> #1 0x00002af27098632c in paircopy2 (vp=0x101010101010101, attr=-1) at valuepair.c:372 first = (VALUE_PAIR *) 0x2aaab0289b60 n = (VALUE_PAIR *) 0x2aaab0289b60 last = (VALUE_PAIR **) 0x2aaab0289b88 #2 0x00002af272007b6e in eaptls_success (handler=0x177ce3a0, peap_flag=0) at eap_tls.c:183 reply = {code = 3 '\003', id = 230 '�', length = 4, flags = 0 '\0', data = 0x0, dlen = 0} vp = (VALUE_PAIR *) 0x101010101010101 vps = (VALUE_PAIR *) 0x0 request = (REQUEST *) 0x2aaab010b880 tls_session = (tls_session_t *) 0x177b4a00 Not sure if it's a new or old bug. Sadly I was using my smartphone from a restaurant to debug (!) and accidentally closed gdb before dumping a core file.