Re: [SR-Users] Child process exited by a signal 11

Yes this makes sense. But higher debug level = more writing. Then increasing the debug level should causes more problem - because more buffering and parsing strings internally, which in turn draws on static (stack) and dynamic (heap) memory allocations - instead of hiding the problem, right? -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Thursday, 20 March 2014 12:06 p.m. To: sr-users(a)lists.sip-router.org Subject: Re: [SR-Users] Child process exited by a signal 11 On 03/19/2014 07:04 PM, Allen Zhang wrote: Well, from a programmatic point of view, not necessarily. Writing debug logs is an operation that involves buffering and parsing strings internally, which in turn draws on static (stack) and dynamic (heap) memory allocations. All of that influences the memory state of the program, and thus has an impact on whether it'll crash, and when it will do so. -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users