Re: crash+backtrace... is it a known issue?

As expected, same crash, essentially the same backtrace. This time I also excluded MySQL from build. ./configure --with-apxs=/usr/local/apache/bin/apxs --without-mysql --enable-debug Fresh today's checkout, apache 1.2.12. So, is this a known issue? If no-one shouts anything legible, I'll just file a bug report and look at it sometime later. Vlad #0 0x4012e0d6 in chunk_free (ar_ptr=0x401c2d60, p=0x8184d38) at malloc.c:3097 #1 0x4012de46 in chunk_alloc (ar_ptr=0x401c2d60, nb=24) at malloc.c:2594 #2 0x4012ee34 in __libc_calloc (n=5, elem_size=4) at malloc.c:3699 #3 0x808d2a0 in zend_hash_init (ht=0x8184d10, nSize=5, pHashFunction=0, pDestructor=0x40223468 <destroy_per_dir_entry>, persistent=1) at zend_hash.c:185 #4 0x402235d2 in php_create_dir (p=0x817c644, dummy=0x0) at mod_php4.c:669 #5 0x80e47f3 in ap_single_module_configure () #6 0x8077730 in load_module () #7 0x80e30ce in invoke_cmd () #8 0x80e39b3 in ap_handle_command () #9 0x80e3a47 in ap_srm_command_loop () #10 0x80e3e50 in ap_process_resource_config () #11 0x80e4712 in ap_read_config () #12 0x80ee729 in main () #13 0x400ec9cb in __libc_start_main (main=0x80ee49c <main>, argc=2, argv=0xbffffad4, init=0x805f3b8 <_init>, fini=0x812294c <_fini>, rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffffacc) at ../sysdeps/generic/libc-start.c:92 Vlad Krupin wrote:

I am pretty sure dbase has nothing to do with it. No dbase code gets called before we crash. I do not think it would make a change. I can rebuild the while thing once again from a clean CVS checkout, and see, I guess, but I am quite sure the issue lies with something else. Vlad Markus Fischer wrote:

On Wed, Nov 28, 2001 at 02:40:55PM -0800, Vlad Krupin wrote :

I finally got around to fixing the dbase bug I have assigned, and... when I tried to compile today's snapshot with a very simple confug line: ./configure --with-apxs=/usr/local/apache/bin/apxs --enable-dbase --enable-debug

Did you test it without '--enable-dbase' ? Same problem? - Markus