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
I may have some cycles tonight as well...
[EMAIL PROTECTED] wrote:
>
>
> I have done just enough looking at this problem to be thoroughly=20
> 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 t
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
Something is hosed (yes, I did a clean rebuild).
I don't really trust this stack trace as ap_log_pid does get a
filename on entry, so I expect that the stack is smashed. I
also ran teststr and that generates a 'bus error.'
I gotta run out the door right now. If no one fixes it by the
time I get
apr-config is giving me -lapr instead of -lapr-0. The attached patch
seems to fix this problem.
--
Scott Lamb
Index: apr-config.in
===
RCS file: /home/cvspublic/apr/apr-config.in,v
retrieving revision 1.22
diff -u -r1.22 apr-config.i