DO NOT REPLY [Bug 8540] - apr_thread_mutex_pool_get segfaults at startup

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8540

apr_thread_mutex_pool_get segfaults at startup

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|httpd could not be started  |apr_thread_mutex_pool_get
   ||segfaults at startup



--- Additional Comments From [EMAIL PROTECTED]  2002-05-25 21:46 ---
Can you please verify that this is still happening with a later version?  The 
backtrace you gave was unfortunately not very helpful because of (apparently) 
some bug in the debugger (which caused all those "internal error" messages).  
If you can still reproduce the problem, can you do it with the --enable-
maintainer-mode configure flag as well?  Also please specify which configure 
flags you used and the output of ./httpd -l and ./httpd -V .

Thanks!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 8540] - apr_thread_mutex_pool_get segfaults at startup

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8540

apr_thread_mutex_pool_get segfaults at startup





--- Additional Comments From [EMAIL PROTECTED]  2002-05-28 15:53 ---
Created an attachment (id=1958)
All logs associated with the build(success)/launch(failure) attempt.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 8540] - apr_thread_mutex_pool_get segfaults at startup

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8540

apr_thread_mutex_pool_get segfaults at startup





--- Additional Comments From [EMAIL PROTECTED]  2002-05-28 16:00 ---
Speaking for myself, I no longer get the thread error, but I'm still not able 
to start httpd.  When I 
attempt to start it (apachectl start), here is the output that appears on my 
screen:

rtld: 
0712-001 Symbol gdbm_errno was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_strerror was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_open was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_close was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_fetch was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_store was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_delete was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_exists was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_firstkey was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-001 Symbol gdbm_nextkey was referenced
  from module 
/export/apache2B/lib/libaprutil.so(), but a runtime definition of the symbol 
was not 
found.

rtld: 0712-002 fatal error: exiting.

My lone argument to configure was the 
"prefix" flag on the first attempt.  My second attempt added the 
"--enable-maintainer_mode", 
which seemed to have no effect ("./httpd -l" and "./httpd -V" produced the same 
output as above).  My 
platform is AIX 4.3.3 with maintenance pack 10 (for the thread issue, I was on 
maintenance level 
9).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]