> I agree that disabling threads is covering up a problem, but I suspect
> that the problem is in glibc and not in Apache.
>
> Some rather lame debug suggestions:
>
> 1) make sure you have the latest glibc... maybe the problem got fixed
Upgrading to the latest glibc does not seem to help.
> 2) make sure you aren't running out of memory
We're not.
> 3) grab the sources for the level of glibc you have and try to get
> some idea of why __pthread_reset_main_thread() might segfault
There seem to be a number of ways that this could dump core and so far
we aren't having any luck tracking this down. The best we can come
up with is that there is some stack corruption happening somewhere.
The latest CVS snapshot seems even more unstable, by the way.
Any other ideas we can chase after?
-adam
--
"I believe in Kadath in the cold waste, and Ultima Thule. But you
cannot prove to me that Harvard Law School actually exists."
- Theodora Goss
"I'm not like that, I have a cat, I don't need you.. My cat, and
about 18 lines of bourne shell code replace you in life."
- anonymous
Adam Sussman
Vidya Media Ventures
[EMAIL PROTECTED]
