https://bz.apache.org/bugzilla/show_bug.cgi?id=58008

--- Comment #12 from Mikhail T. <[email protected]> ---
With the patch applied, the crash happens a few steps later, when the
interpreter itself is deleted:

#0  0x00000008019501aa in thr_kill () from /lib/libc.so.7
#1  0x0000000801950116 in raise () from /lib/libc.so.7
#2  0x000000080194e8f9 in abort () from /lib/libc.so.7
#3  0x0000000808b7d08f in ?? () from /opt/libexec/apache24/mod_rivet.so
#4  0x00000008088e0d84 in Tcl_PanicVA (format=<optimized out>,
argList=<optimized out>)
    at /home/ports/lang/tcl86/work/tcl8.6.4/generic/tclPanic.c:99
#5  0x00000008088e0e72 in Tcl_Panic (format=0x18b90 <error: Cannot access
memory at address 0x18b90>)
    at /home/ports/lang/tcl86/work/tcl8.6.4/generic/tclPanic.c:153
#6  0x000000080881a60f in Tcl_AsyncDelete (async=0x8024fbed0) at
/home/ports/lang/tcl86/work/tcl8.6.4/generic/tclAsync.c:283
#7  0x000000080881c021 in DeleteInterpProc (interp=0x81c582010)
    at /home/ports/lang/tcl86/work/tcl8.6.4/generic/tclBasic.c:1423
#8  0x0000000808b7c90f in ?? () from /opt/libexec/apache24/mod_rivet.so
#9  0x00000008011b24be in apr_pool_destroy () from /opt/lib/libapr-1.so.0
#10 0x0000000805733872 in clean_child_exit (code=0) at prefork.c:218
#11 0x0000000805733807 in just_die (sig=15) at prefork.c:344
#12 0x00000008015f38eb in ?? () from /lib/libthr.so.3
#13 0x00000008015f2ffc in ?? () from /lib/libthr.so.3
#14 <signal handler called>
#15 0x000000080195136a in _select () from /lib/libc.so.7
#16 0x00000008015f0f72 in ?? () from /lib/libthr.so.3
#17 0x000000080891be70 in NotifierThreadProc (clientData=<optimized out>) at
tclUnixNotfy.c:1216
#18 0x00000008015ee775 in ?? () from /lib/libthr.so.3
#19 0x0000000000000000 in ?? ()

> Are you running Apache 2.2 or 2.4? Which patchlevel version exactly?

Using apache-2.4.12.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to