I finally came around to reinstalling but sadly it didn't help. I still get
the exact same core dumps :-/
If anyone else has experienced similiar issues I would be grateful for some
input.
Caveat: I am one data point, I recently had the problem, and a rebuild
solved it for me. That doesn't mean
I'm trying to investigate some core dumps in mod_security and currently
face this
(gdb) bt
#0 0xf6efc232 in create_tx_context (r=0x1eac8ed0) at mod_security2.c:325
#1 0xf6efc606 in hook_error_log (file=0x80a51bd http_filters.c,
line=493, level=3, status=104, s=0x18144178, r=0x1eac8ed0, mp=0x0,
On 24 May 2013, at 10:38 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote:
Why would the per_dir_config be NULL here ? I don't think that should ever be
encountered during the request's lifetime, right ?
I had this recently, and a completely clean rebuild sorted it out.
Regards,
Graham
--
How did you investigate into this ? I'll assume with rebuild you mean you
rebuilt apache2 from source and reinstalled it. What made you rebuild it in
this scenario ? Also, why do you think rebuilding solved it ? I'm being so
specific about investigation options since rebuilding and reinstalling it
On 24 May 2013, at 11:03 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote:
How did you investigate into this ? I'll assume with rebuild you mean you
rebuilt apache2 from source and reinstalled it. What made you rebuild it in
this scenario ?
Yes, in my case the module that was returning
