Segfault in __pthread_mutex_lock

[Shevek <sh...@tirin.openworld.co.uk>]

I have a nasty feeling this might be the RULE_EXPAT thing, I didn't do a
RULE_EXPAT=no when building Apache. Is there documentation describing the
dirty details of the issue? Can anybody confirm?

Program received signal SIGSEGV, Segmentation fault.
__pthread_mutex_lock (mutex=0x410) at mutex.c:82
82      mutex.c: No such file or directory.
(gdb) bt
#0  __pthread_mutex_lock (mutex=0x410) at mutex.c:82
#1  0x40168233 in free () from /lib/libc.so.6
#2  0x8164cc0 in Perl_safefree ()
#3  0x815a02c in Perl_op_free ()
#4  0x8159f15 in Perl_op_free ()
#5  0x8159f15 in Perl_op_free ()
#6  0x8159f15 in Perl_op_free ()
#7  0x815e250 in Perl_cv_undef ()
#8  0x817623a in Perl_sv_clear ()
#9  0x81763f2 in Perl_sv_free ()
#10 0x8146e2a in Perl_gv_fetchmeth ()
#11 0x81471e5 in Perl_gv_fetchmethod_autoload ()
#12 0x8147128 in Perl_gv_fetchmethod ()
#13 0x817251b in Perl_pp_method ()
#14 0x819b8f6 in Perl_runops_standard ()
#15 0x8144559 in perl_call_sv ()
#16 0x80ee93b in perl_call_handler ()
#17 0x80ee306 in perl_run_stacked_handlers ()
#18 0x80ed259 in perl_handler ()
#19 0x8105a23 in ap_invoke_handler ()
#20 0x8118cdd in process_request_internal ()
#21 0x8118d3c in ap_process_request ()
#22 0x81106d1 in child_main ()
---Type <return> to continue, or q <return> to quit---
#23 0x8110864 in make_child ()
#24 0x81109bf in startup_children ()
#25 0x8110fe4 in standalone_main ()
#26 0x8111763 in main ()
#27 0x401292e7 in __libc_start_main () from /lib/libc.so.6
(gdb) frame 0
#0  __pthread_mutex_lock (mutex=0x410) at mutex.c:82
82      in mutex.c
(gdb) info locals 
mutex = (pthread_mutex_t *) 0x410
self = 0x0

S.

--
Shevek

It's not an infinite loop! It's just a state with which I was not
previously familiar.

$/="";$_=<>;s/([A-Ya-z]+)\b/$1Z/g;print;

Re: Segfault in __pthread_mutex_lock

[Doug MacEachern <do...@covalent.net>]

On Thu, 13 Apr 2000, Shevek wrote:

> I have a nasty feeling this might be the RULE_EXPAT thing, I didn't do a
> RULE_EXPAT=no when building Apache. Is there documentation describing the
> dirty details of the issue? Can anybody confirm?

well, are you using XML::Parser?  if so, why not confirm yourself by
trying RULE_EXPAT=no?