ng mix of ports & packages in prod, perhaps with some pkg
> lock, on the grounds that we know it works and we can roll forward to a better
> solution when one comes out soon. I have done worse things in the past.
>
> I hope this makes sense.
>
> - Alex
>
>
> On 7/
On 7/18/25 13:35, Randolf Richardson via modperl wrote:
On Jul 17, 2025, at 1:32PM, Alex Aminoff wrote:
I have written up a description and replication code here:
http://back.nber.org/sys-admin/apache2_upload_bug.html
Is this something anyone else has seen?
Hi, Alex. Yes, this is a known
I have written up a description and replication code here:
http://back.nber.org/sys-admin/apache2_upload_bug.html
Is this something anyone else has seen?
Thanks,
- Alex Aminoff
NBER
with $/, we went from
dozens of seg faults per hour to none.
- Alex Aminoff
BaseSpace.net
National Bureau of Economic Research (nber.org)
On Tue, 12 Jan 2010, Mark Copper wrote:
Hi,
I have a server like this:
Server Version: Apache/2.2.9 (Debian) mod_ssl/2.2.9 OpenSSL/0.9.8g
On Thu, 31 Dec 2009, Philippe M. Chiasson wrote:
On 09-12-31 12:52 , Alex Aminoff wrote:
Most certainly, yes. A stack trace without debugging symbols is not
very useful in trying to pin down the source of a segfault bug.
OK, I compiled mod_perl with MP_DEBUG and MP_TRACE, and
got apache
Most certainly, yes. A stack trace without debugging symbols is not
very useful in trying to pin down the source of a segfault bug.
OK, I compiled mod_perl with MP_DEBUG and MP_TRACE, and
got apache to produce a core dump (kern.sugid_coredump=1 appears to
be needed on FreeBSD):
(gdb) bt
#0
2 : -
Apache2::Request : 2.12
CGI: 3.42
ExtUtils::MakeMaker: 6.48, undef
LWP: 5.834
mod_perl : -
mod_perl2 : 2.04
3. This is the core dump trace: (if you get a core dump):
[CORE TRACE COMES HERE]
This report was generated by /usr/local/bin/mp2bug on Wed Dec 30 20:46:25 2009
GMT.
- Alex Aminoff
BaseSpace.net
National Bureau of Economic Research (nber.org)
