kdeinit problems in 3.7-current

[Josh Grosse <josh_(_at_)_jggimi_(_dot_)_homeip_(_dot_)_net>]

OS: 3.7-current as of July 12, with sync-ed kernel, userland, XF4, and ports
App:  kdebase-3.4.1, rebuilt 7/13, after building kernel, userland, XF4.
Platform: i386

This newbie is looking for debugging advice.  I'm not sure exactly where to
look to try to solve this particular software problem.  I'm looking for 
advice as to which FM to RT.  :-)

-----------------------------------------------------------------------------
Usually when I'm using firefox 1.0.4, my X environment will crash.
Each time, kdeinit drops a .core file showing:
-----
	#0  0x099e50d1 in kill () from /usr/lib/libc.so.38.1
-----

Immediately afterwards, Xorg would report "caught signal 11" -- both on the
startx console, and, in the Xorg.0.log file.  Now, because signal 11s
are so often hardware problems, I ran memtest86 on the hardware.  12 hours of
running memtest86 does not show any obvious memory problems.

My xorg.conf file is automatically generated with xorgcfg.  I added these lines
to get Xorg to drop a .core file as well:
-----
	Section "ServerFlags"
        	Option "NoTrapSignals" "on"
	EndSection
-----

Kdeinit still drops a core file, but Xorg does not.  But, the console messages
and log messages have changed.  Now, the log does not show any messages at 
failure ... the file is just closed when Xorg stops running.  And the console,
instead of showing "signal 11", shows:
-----
	Gdk-ERROR **: X connection to :0.0 broken (explicit kill 
	or server shutdown).
-----

I'm not sure whether this is an Xorg issue, a KDE issue, or -- because I'm
running firefox, an X application issue.  Any advice you might have to help
me narrow down the problem further would be appreciated.

   -Josh-