It turns out that httpd 2.2.18 has a binary ABI breakage bug which
will require a re-roll. If we have our 1.4.4/1.3.11 regressions
(Windows debug log, ldap pool cleanup, fnmatch edge case) resolved in
new releases in time, that would be great for all.
If you're aware of any regressions for which
On Wed, 2011-05-18 at 14:20 -0400, Jeff Trawick wrote:
It turns out that httpd 2.2.18 has a binary ABI breakage bug which
will require a re-roll. If we have our 1.4.4/1.3.11 regressions
(Windows debug log, ldap pool cleanup, fnmatch edge case) resolved in
new releases in time, that would be
On Wed, May 18, 2011 at 2:45 PM, Mike Jakubik
mike.jaku...@intertainservices.com wrote:
On Wed, 2011-05-18 at 14:20 -0400, Jeff Trawick wrote:
It turns out that httpd 2.2.18 has a binary ABI breakage bug which
will require a re-roll. If we have our 1.4.4/1.3.11 regressions
(Windows debug
On 2011-05-18 20:20, Jeff Trawick wrote:
It turns out that httpd 2.2.18 has a binary ABI breakage bug which
will require a re-roll. If we have our 1.4.4/1.3.11 regressions
(Windows debug log, ldap pool cleanup, fnmatch edge case) resolved in
new releases in time, that would be great for all.
On Wed, 2011-05-18 at 00:53 +0200, Rainer Jung wrote:
GDB allows to also get details on the values of variables used, step
through the code etc. You give gdb two arguments, the path to your httpd
binary and the process ID of the CPU consuming process. Once the gdb
prompt is shown, you can
On Wed, May 18, 2011 at 2:57 PM, Mike Jakubik
mike.jaku...@intertainservices.com wrote:
On Wed, 2011-05-18 at 00:53 +0200, Rainer Jung wrote:
GDB allows to also get details on the values of variables used, step
through the code etc. You give gdb two arguments, the path to your httpd
binary
