apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Blair Zajac <bl...@orcaware.com>
Subject Re: Segfault in ap_vformatter on httpd startup
Date Tue, 27 Aug 2002 01:09:30 GMT
Aaron Bannert wrote:
> 
> On Mon, Aug 26, 2002 at 06:04:28PM -0400, Ryan Bloom wrote:
> > I have done just enough looking at this problem to be thoroughly
> > confused.  Basically, if I run test/teststr, I get the seg fault, but if
> > I run test/.libs/teststr, everything just works.  I have re-built
> > multiple times, so I am at a complete loss here.  I'll try to look at this
> > later tonight when I get home.
> 
> Did you rebuild and install? The test/.libs/teststr one should be linked
> against the installed version, while the test/teststr should set up your
> dynamic link path to work with the libapr in your build tree.

I'm seeing a core dump in Subversion revision 3073 at the same location,
clean build, everything.  Reproducible by running

% cd subversion/tests/clients/cmdline
% python2 trans_tests.py 1

Running valgrind on teststr gets this:

Testing precision  ........
==14401== Conditional jump or move depends on uninitialised value(s)
==14401==    at 0x402685B0: apr_vformatter (apr_snprintf.c:1220)
==14401==    by 0x4026871C: apr_snprintf (apr_snprintf.c:1268)
==14401==    by 0x8048AEF: test_snprintf (teststr.c:138)
==14401==    by 0x8048BD4: main (teststr.c:163)
==14401==
==14401== Use of uninitialised value of size 4
==14401==    at 0x4026872A: apr_snprintf (apr_snprintf.c:1271)
==14401==    by 0x8048AEF: test_snprintf (teststr.c:138)
==14401==    by 0x8048BD4: main (teststr.c:163)
==14401==    by 0x42017589: (within /lib/i686/libc-2.2.5.so)
==14401==
==14401== Invalid write of size 1
==14401==    at 0x4026872A: apr_snprintf (apr_snprintf.c:1271)
==14401==    by 0x8048AEF: test_snprintf (teststr.c:138)
==14401==    by 0x8048BD4: main (teststr.c:163)
==14401==    by 0x42017589: (within /lib/i686/libc-2.2.5.so)
==14401==    Address 0x0 is not stack'd, malloc'd or free'd
Segmentation fault (core dumped)

I spent a while looking at the first warning and I'm not convinced it's
causing the problem, but it would be good to clean up.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/

Mime
View raw message