DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38403>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38403





------- Additional Comments From [EMAIL PROTECTED]  2006-02-04 12:02 -------
we were unable to ltrace the processes (ltrace returns without error, and
sometimes kills the amok process). we found out from looking at /proc, that it
is not the allocator_free thread which consumes the cpu, but the
core_input_filter thread (telling from the SleepAVG in /proc/PID/status).

we recompiled with -ggdb and obtained more infos at the next occurence of the
phenomenon. 

(gdb) info threads
  3 Thread -2063254608 (LWP 9309)  allocator_free (allocator=0x195737d0,
node=0xa52eec0) at memory/unix/apr_pools.c:332
  2 Thread 1801628592 (LWP 9350)  0x0807af5b in ap_core_input_filter
(f=0x195740b8, b=0x9feddc8, mode=AP_MODE_GETLINE, block=APR_BLOCK_READ, 
readbytes=0)
    at core_filters.c:141
  1 Thread -1210169664 (LWP 9228)  0xb7f09402 in __kernel_vsyscall ()

I attach a complete backtrace to this bug. Bottom line is, that we are stuck on
this line: 

ap_core_input_filter (f=0x195740b8, b=0x9feddc8, mode=AP_MODE_GETLINE,
    block=APR_BLOCK_READ, readbytes=0) at core_filters.c:141
141         BRIGADE_NORMALIZE(ctx->b);


code says this:

    /* ### This is bad. */
    BRIGADE_NORMALIZE(ctx->b);


but I'm not sure whether "this is bad" refers to a possible bug or just a
performance issue. 

Is there a simple way to inspect the BRIGADE in gdb ? I guess there's a special
situation with the brigade or its buckets, that arives from the fact that we run
the http-backend on localhost (probably caused by unusual/local tcp behaviour ?)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to