[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read How to report bugs effectively

[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread martin suc
I have attached very detailed crash report - see #1 , it contains a lot of useful debugging information - stack trace , coredump, library dump, memory dump and many further information. Answer to questions: 1. the specific steps or actions you took that caused you to encounter the problem, no

[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread Robie Basak
Thanks for your reply. The link to the upstream bug is very helpful, and I appreciate that you had attached the crash report. no specific steps or actions from my side at all. What we're after is an explanation of how to reproduce the bug. If you'd like an update to 12.10, then we need exact

[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read How to report bugs effectively

[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread martin suc
I have attached very detailed crash report - see #1 , it contains a lot of useful debugging information - stack trace , coredump, library dump, memory dump and many further information. Answer to questions: 1. the specific steps or actions you took that caused you to encounter the problem, no

[Bug 1131115] Re: php5-fpm crashed with SIGSEGV in munmap()

2013-02-25 Thread Robie Basak
Thanks for your reply. The link to the upstream bug is very helpful, and I appreciate that you had attached the crash report. no specific steps or actions from my side at all. What we're after is an explanation of how to reproduce the bug. If you'd like an update to 12.10, then we need exact