MACHINE_ARCH:	i386
mozilla:	1.3 from pkgsrc, built March 30

   Mozilla had been running fine, but running the same mozilla
against a current kernel and userland as of late yesterday, I get
a seg fault, and running under gdb shows the following stack:

===========================================================================
#0  0x8072dde in NS_GetMemoryManager ()
#1  0x8072e00 in NS_GetMemoryManager ()
#2  0x8072e00 in NS_GetMemoryManager ()
#3  0x8072e00 in NS_GetMemoryManager ()
#4  0x8072e00 in NS_GetMemoryManager ()
#5  0x8072e00 in NS_GetMemoryManager ()
#6  0x8072e00 in NS_GetMemoryManager ()
#7  0x8072e00 in NS_GetMemoryManager ()
#8  0x8072e00 in NS_GetMemoryManager ()
#9  0x8072e00 in NS_GetMemoryManager ()
#10 0x8072e00 in NS_GetMemoryManager ()
[ ... ]
#5230 0x8072e00 in NS_GetMemoryManager ()
#5231 0x8072e00 in NS_GetMemoryManager ()
#5232 0x8072e00 in NS_GetMemoryManager ()
#5233 0x8072e00 in NS_GetMemoryManager ()
#5234 0x8072e00 in NS_GetMemoryManager ()
#5235 0x8072e00 in NS_GetMemoryManager ()
#5236 0x807243a in GlueStartupMemory ()
#5237 0x8072c22 in XPCOMGlueStartup ()
#5238 0x8072f21 in GRE_Startup ()
#5239 0x805876d in main ()
#5240 0x8053f84 in ___start ()
===========================================================================

   First of all, I'm impressed that it managed over 5000 stack
frames before dying. Secondly, I'm impressed that gdb didn't give
up before showing all the frames. Finally, I'd like to find out
why it is doing this and if it can be fixed. FWIW, Netscape 4 and
7 binaries for Linux from pkgsrc are still working.

   Actually, now that I glance at the code, I don't know why it
didn't always do this. Anyone know what is going on here?

					Gary Duzan