[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Apache 2.0.50-8 upgrade breaks WebDAV (?)



Okay, let me correct myself a bit, as I was thinking backwardly in my previous post:

apache2-mpm-prefork 2.0.50-8

amd64:
# nm -D /usr/sbin/apache2 | grep ap_register
0000000000422dd0 T ap_register_hooks
000000000042e960 T ap_register_input_filter
000000000042e970 T ap_register_output_filter
0000000000437910 T ap_register_request_note

i386:
# nm -D /usr/sbin/apache2 | grep ap_register
080aa6e8 D ap_hack_ap_register_hooks
080aaba0 D ap_hack_ap_register_input_filter
080aaba4 D ap_hack_ap_register_output_filter
080aa658 D ap_hack_ap_register_provider
080aa804 D ap_hack_ap_register_request_note
080788e0 T ap_register_hooks
080855f0 T ap_register_input_filter
08085630 T ap_register_output_filter
080922e0 T ap_register_provider                             <--------------
0808eb50 T ap_register_request_note

So, the WebDAV stuff works on my pentium machines, but not on the opteron machine since mod_dav.so calls ap_register_provider in
modules/dav/main/providers.c

I built 2.0.50-8 from source on the opteron box and got the same result (ap_register_provider symbol undefined)

My interest in now piqued.  As I'm not on top of debian development, where can I find a diff between 2.0.50-7 and -8 ?
-dh



On Fri, 2004-08-13 at 07:00, Dan Hugo wrote:
Hello Philipp--

2.0.50-7 was definitely working for me.  I don't recall if it was -6 or older that had an issue with DAV just not working at all, but -7 was definitely working well.

However, on upgrading to 2.0.50-8, that no longer appears to be the case.

Hmmmm, I just did a quick little "ldd" survey:

# ldd /usr/lib/apache2/modules/mod_dav.so
        libdl.so.2 => /lib/libdl.so.2 (0x0000002a95679000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0x0000002a9577d000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x0000002a9589f000)
        libdb-4.2.so => /usr/lib/libdb-4.2.so (0x0000002a959d2000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0000002a95bb1000)
        libc.so.6 => /lib/libc.so.6 (0x0000002a95d46000)
        /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000)

# ldd /usr/lib/apache2/modules/mod_dav_svn.so | grep libapr
        libaprutil-0.so.0 => /usr/lib/libaprutil-0.so.0 (0x0000002a95ec0000)
        libapr-0.so.0 => /usr/lib/libapr-0.so.0 (0x0000002a96520000)

(the result list for the latter is much larger, hence the grep)

Since ap_register_provider is in libapr-0 (if memory serves), is this a problem?

It's been a long time since I debugged libs and compiled code (doing mostly sql/python/php/etc lately), so forgive my slowness on the uptake...

thanks
-dh

On Fri, 2004-08-13 at 06:32, Philipp Frauenfelder wrote:
Hi Dan

Apache 2.0.50-7 from
http://debian.inode.at/pure64/pool/unstable/main/amd64/a/apache2/
worked for me (with svn / WebDAV).

Regards 

Reply to: