Hi, I had a similar problem with mod_macro when I put _a_ Use statement before _all_ Macro definition (if any).
The problem is that the apache hook for initialising some memory (the 'init' function) is not functioning, so the init is not called at the beginning. Somehow someone noticed it crashed because the memory wasn't allocated, and added a check in the 'section' function (for processing a <macro> directive) which calls init if the memory isn't allocated. This is obviously a dirty fix. All goes well, until you put a Use statement first. No check there (function get_macro_by_name), null pointer is spotted and an assertion fails. I've been looking around a bit on google and apache.org for issues with that hook (ap_hook_pre_config), but no luck. To be able to check this behaviour without messing up with versions: apt-get source libapache2-mod-macro cd liba... edit debian/rules: line 14: $(APXS) -D MOD_MACRO_DEBUG=1 -c mod_macro.c edit debian/changelog to bump up the version dpkg-buildpackage -us -uc -rfakeroot dpkg -i ../liba... You'll see that init only gets called when it first enters a section. -- Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
