Subject: port-pmax/5064: twm is coredumping under 1.3 on pmax
To: None <>
From: Aaron J. Grier <>
List: netbsd-bugs
Date: 02/24/1998 19:04:08
>Number:         5064
>Category:       port-pmax
>Synopsis:       twm is segfaulting when running Netscape 4.04 client on osf1
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 24 19:05:00 1998
Reed College Academic Software Development Lab
>Release:        NetBSD 1.3 (GENERIC) #2: Tue Dec 30 01:16:36 PST 1997
System: NetBSD durga 1.3 NetBSD 1.3 (GENERIC) #2: Tue Dec 30 01:16:36 PST 1997 jonathan@Reno.DSG.Stanford.EDU:/reno/compile/GENERIC pmax

twm running on a PMIN is coredumping when attempting to run the
Netscape 4.04 osf1 client.

This does _not_ appear to be a problem with the Xserver itself, but just in
case you're wondering, I'm running Xmfbpmax on the monochrome baseboard 
video on a 2100 with 12mb of RAM.

gdb output looks like this:

Attaching to program `/usr/X11R6/bin/twm', process 14393
0x203f0264 in ?? ()
(gdb) set heuristic-fence-post 32767
(gdb) cont
[fire up netscape]
Program received signal SIGSEGV, Segmentation fault.
0x2034b9e8 in ?? ()
(gdb) bt
#0  0x2034b9e8 in ?? ()
#1  0x2034bb28 in ?? ()
#2  0x420f64 in HandleEvents ()

I have a coredump if you'd like it, and could recompile twm to get the
symbols...  (Right now I'm recompiling fvwm2, since it exhibits similar
behaviour, but that's the subject of another PR...)

If anybody has an unstripped twm they'd like to build for me on a faster
machine, I'd be happy to try it out.

dust off your 2100, fire it up, and run the navigator-4.04 osf1 client on
an alpha near you.  Watch twm dump core.

don't run a local window manager.  :)