You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Sander Temme <sc...@apache.org> on 2005/10/12 17:20:40 UTC
Core dump on ajax: crash in mod_mbox
The httpd-2.0.55 RC currently running on ajax had a segfault about an
hour ago, here's the backtrace.
Looks like a crash in mod_mobx, so I don't think it affects the httpd
release.
#0 0x20000000009f30a0 in strlen () from /lib/tls/libc.so.6.1
#1 0x20000000010109f0 in mbox_mime_decode_multipart
(p=0x60000000002147c8,
body=0x6000000000294d25 "Content-Type: application/octet-stream
\nContent-Transfer-Encoding: base64\nContent-Disposition: attachment
\n filename=HelloServer.wsdl;
\nPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjx3c2RsOmRlZml"..
.,
ct=0x0, cte=CTE_NONE, boundary=0x0) at mod_mbox_mime.c:28
#2 0x20000000010107d0 in mbox_mime_decode_multipart
(p=0x60000000002147c8,
body=0x10 <Address 0x10 out of bounds>,
ct=0x6000000000296e1e "--73b855d461231501\nContent-Type:
application/octet-stream\nContent-Transfer-Encoding: base64\nContent-
Disposition: attachment; filename=generated.wsdl\n
\nPHdzZGw6ZGVmaW5pdGlvbnMgdGFyZ2V0TmFtZXNwYWNlPSJodH"...,
cte=410720, boundary=0x2d <Address 0x2d out of bounds>)
at mod_mbox_mime.c:231
#3 0x200000000100cda0 in mbox_static_message (r=0x6000000000214830,
f=0x6000000000233b98) at mod_mbox_out.c:1070
#4 0x2000000001008ca0 in mbox_file_handler (r=0x6000000000214830)
at mod_mbox_file.c:231
#5 0x4000000000035f90 in ap_run_handler (r=0x6000000000214830) at
config.c:153
#6 0x4000000000036f70 in ap_invoke_handler (r=0x6000000000214830)
at config.c:317
#7 0x400000000002fb00 in ap_process_request (r=0x6000000000214830)
at http_request.c:226
#8 0x4000000000024bf0 in ap_process_http_connection
(c=0x60000000001db330)
at http_core.c:233
#9 0x400000000004db00 in ap_run_process_connection
(c=0x60000000001db330)
at connection.c:43
#10 0x4000000000032910 in child_main (child_num_arg=27976) at
prefork.c:610
#11 0x4000000000032be0 in make_child (s=0x6000000000047788, slot=428)
at prefork.c:704
#12 0x4000000000033180 in perform_idle_server_maintenance (p=0x15)
at prefork.c:839
#13 0x4000000000033fc0 in ap_mpm_run (_pconf=0x0,
plog=0x6000000000042298,
s=0x0) at prefork.c:863
#14 0x4000000000041f60 in main (argc=2, argv=0x60000fffffff9dd8) at
main.c:618
--
sander@temme.net http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
Re: Core dump on ajax: crash in mod_mbox
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Wed, Oct 12, 2005 at 01:31:42PM -0700, Sander Temme wrote:
> There is now:
>
> [Wed Oct 12 22:04:43 2005] [notice] child pid 5885 exit signal =20
> Segmentation fault (11), possible coredump in /raid1/httpd-cores
>
> Backtrace:
...
> Note, this was /raid1/httpd-cores/core.5885 .
(gdb) print r->unparsed_uri
$2 =3D 0x6000000000251f00
"/mod_mbox/httpd-users/200310.mbox/%3CBAY2-F103MOEYzk8TRA00006ddd@hotmail.c=
om%3E"
I'll see what I can do about reproducing here; but I've got to leave in
an hour or so. -- justin
Re: Core dump on ajax: crash in mod_mbox
Posted by Sander Temme <sc...@apache.org>.
On Oct 12, 2005, at 12:40 PM, Justin Erenkrantz wrote:
> On Wed, Oct 12, 2005 at 08:20:40AM -0700, Sander Temme wrote:
>
>
>> The httpd-2.0.55 RC currently running on ajax had a segfault about an
>> hour ago, here's the backtrace.
>>
>> Looks like a crash in mod_mobx, so I don't think it affects the httpd
>> release.
>>
>>
>
> Paul, Sam, and I analyzed the cores and committed some fixes. Those
> changes are now deployed on ajax. No cores yet. -- justin
>
There is now:
[Wed Oct 12 22:04:43 2005] [notice] child pid 5885 exit signal
Segmentation fault (11), possible coredump in /raid1/httpd-cores
Backtrace:
#0 mbox_mime_decode_body (p=0x0, cte=CTE_NONE, body=0x0, len=0)
at mod_mbox_mime.c:290
#1 0x2000000001011110 in mbox_mime_get_body (p=0x60000000002509c8,
m=0x6000000000063130) at mod_mbox_mime.c:299
#2 0x200000000100d2e0 in mbox_static_message (r=0x6000000000250a30,
f=0x60000000001ed530) at mod_mbox_out.c:1151
#3 0x2000000001008ca0 in mbox_file_handler (r=0x6000000000250a30)
at mod_mbox_file.c:231
#4 0x4000000000035f90 in ap_run_handler (r=0x6000000000250a30) at
config.c:153
#5 0x4000000000036f70 in ap_invoke_handler (r=0x6000000000250a30)
at config.c:317
#6 0x400000000002fb00 in ap_process_request (r=0x6000000000250a30)
at http_request.c:226
#7 0x4000000000024bf0 in ap_process_http_connection
(c=0x60000000001db350)
at http_core.c:233
#8 0x400000000004db00 in ap_run_process_connection
(c=0x60000000001db350)
at connection.c:43
#9 0x4000000000032910 in child_main (child_num_arg=27976) at
prefork.c:610
#10 0x4000000000032be0 in make_child (s=0x6000000000047788, slot=360)
at prefork.c:704
#11 0x4000000000033180 in perform_idle_server_maintenance (p=0x6)
at prefork.c:839
#12 0x4000000000033fc0 in ap_mpm_run (_pconf=0x600000000000bc68,
plog=0x6000000000042298, s=0x0) at prefork.c:863
#13 0x4000000000041f60 in main (argc=2, argv=0x60000fffffffb3e8) at
main.c:618
Note, this was /raid1/httpd-cores/core.5885 .
It seems that httpd itself holding up well.
S.
--
sander@temme.net http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
Re: Core dump on ajax: crash in mod_mbox
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Wed, Oct 12, 2005 at 08:20:40AM -0700, Sander Temme wrote:
> The httpd-2.0.55 RC currently running on ajax had a segfault about an
> hour ago, here's the backtrace.
>
> Looks like a crash in mod_mobx, so I don't think it affects the httpd
> release.
Paul, Sam, and I analyzed the cores and committed some fixes. Those
changes are now deployed on ajax. No cores yet. -- justin