2008/1/3, Fabio Margarido <[EMAIL PROTECTED]>: > > You can use tport tags TPTAG_UDP_RMEM() and TPTAG_UDP_WMEM() to adjust > > the amount of buffer space. On Linux systems, you should also consider > > adjusting rmem and wmem sysctls. > > > > --Pekka > > I'll try fiddling with those, but in the meantime I had changed the > values for TPTAG_THRPSIZE and TPTAG_THRPRQSIZE and it seemed to help. > I haven't had any more of those buffer-related problems, but it is > possible that they have only been postponed, because my application > keeps crashing. I'm still getting SIGSEGVs like the one below:
> You've told me before that they are probably related to some memory > overrun. I've ran my application under valgrind and there were no > errors reported for a single call, so I'm guessing it's something > related to concurrency under heavy load. Could you please try to give > me a hint of what I could be doing to overflow the stack's memory > space? I have no idea. It seems to be that your problem is because the freelist is corrupted, and it should be possible to detect that with valgrind. Are you using NDEBUG? By default, the stack fills the freed memory with garbage, but if you have NDEBUG defined, it does not. --Pekka -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
