DO NOT REPLY [Bug 41326] - Memory Leak

[bu...@apache.org]

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=41326>.
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=41326





------- Additional Comments From greg.stump@hsc.utah.edu  2007-08-03 15:16 -------
I have generated a backtrace following the instructions posted at 
http://httpd.apache.org/dev/debugging.html#backtrace-win and have the 
drwtsn32.log file, as well as, the user.dmp file.  I'm interested in this 
topic because our organization's Apache 2.2.4 installations on Windows 2003 
server are setup similar to what is described above and having similar 
problems, what exactly are we seeking in the backtrace?  It is nearly 2 MB in 
size.

(In reply to comment #7)
> The -backtrace- I refer to is spelled out at
> http://httpd.apache.org/dev/debugging.html#backtrace-win
> note you don't want the 'live' backtrace, but the faulted backtrace from the
> crash (immediately before the runaway memory problem)
> What your oodles of information do -not- convey is which thread crashed
> (there will be a FAULT >>> comment next to the offending bytecode) and the
> backtrace of which function called which function called which function which
> then faulted.  *that's* what we want to see to help you further.



-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org