DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42262>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42262 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW ------- Additional Comments From [EMAIL PROTECTED] 2007-06-25 07:22 ------- Hello Ruediger, there are no ulimts defined and the physical memory did not go out of limits during the crash. A test with defining explicitly 'ulimit -a' before starting apache gave the same result. But anyway, if a thread cannot allocate memory, malloc (or whatever function is used) should be checked whether the operation was succesful. A segmentation-fault is to me like a hint to a programm error or at least some sign for "quick & dirty" hacked code. Maybe you can find the piece of code where the memory allocation is not checked against the return value? Thanks and greetings Roger -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
