Unless I'm doing something wrong with gdb, they're not very useful. Here's a backtrace from core.11358:
#0 mbox_cte_escape_html (p=0x6000000000548188,s=0x60000000004e4ea8 '-' <repeats 200 times>..., len=18446744073709551522,
body=0x60000000002b94d8) at mod_mbox_cte.c:82
#1 0x2000000001021600 in mbox_mime_display_static_structure (
r=0x6000000000548188, m=0x60000000002b94d8,
link=0x200000000103e938 "")
at mod_mbox_mime.c:362
From frame 1:
(gdb) print r->finfo->fname
$3 = 0x600000000053a157 "/<OF8CDE9A2E.B34E06CD-ON80256FCB.
[EMAIL PROTECTED]>"
Otherwise, the request_rec appears full of garbage. I don't know if this is because the server was built with -g -O2. Perhaps I need to load the module text before I can get meaningful data out of gdb?
core.6672: (gdb) bt #0 mbox_cte_escape_html (p=0x60000000003311a8,s=0x60000000005df628 '-' <repeats 200 times>..., len=18446744073709551522,
body=0x60000000004bd498) at mod_mbox_cte.c:82
#1 0x2000000001021600 in mbox_mime_display_static_structure (
r=0x60000000003311a8, m=0x60000000004bd498,
link=0x200000000103e938 "")
at mod_mbox_mime.c:362
Previous frame inner to this frame (corrupt stack?)
(gdb) print r->finfo->fname
$1 = 0x600000000041b937 "/<OF8CDE9A2E.B34E06CD-ON80256FCB.
[EMAIL PROTECTED]>"
Looks like the same as above. Note the remark about the possibility of stack corruption. Do we have something overwriting the stack frame?
The other three cores are for the same fname. Wonder what mail that is that seems to reproducably crash mod_mbox.
The httpd-2.2.0 I just installed is running the same mod_mbox code, so it's not unlikely that we'll see this happen again.
S. -- [EMAIL PROTECTED] http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
smime.p7s
Description: S/MIME cryptographic signature
