From owner-freebsd-smp  Mon Nov 24 21:15:35 1997
Return-Path: <owner-freebsd-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA11716
          for smp-outgoing; Mon, 24 Nov 1997 21:15:35 -0800 (PST)
          (envelope-from owner-freebsd-smp)
Received: from nomis.Simon-Shapiro.ORG (nomis.i-Connect.Net [206.190.143.100])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA11668
          for <freebsd-smp@freebsd.org>; Mon, 24 Nov 1997 21:15:27 -0800 (PST)
          (envelope-from shimon@nomis.Simon-Shapiro.ORG)
Received: (qmail 12342 invoked by uid 1000); 25 Nov 1997 05:13:36 -0000
Message-ID: <XFMail.971124211336.shimon@Simon-Shapiro.ORG>
X-Mailer: XFMail 1.2-beta-111797 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Mon, 24 Nov 1997 21:13:36 -0800 (PST)
Reply-To: shimon@simon-shapiro.org
Organization: Me, Just me...
From: Simon Shapiro <shimon@simon-shapiro.org>
To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org,
        freebsd-smp@freebsd.org
Subject: Compiler Bug???
Sender: owner-freebsd-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I hope someone reads this and actually responds.

I cross-mail to these lists as some people I am trying to reach do not
read either of these lists and it touches all (I think).

O/S:  FreeBSD 3.0-current as of last few days.  X11 3.3.1, compiled here
(mainly to get rid of the libtermcap problem).

Scenario 1:

Xfmail of 17-Nov-97 with xforms 0.88:  Compiles fine, then produces
dozens of ``Bad Attribute'' and `Bad Coordinates''.  These come from
libX11.  Tearing my hair out did not help, so I boot UP (was on SMP).
The problem is... GONE!

Recompile on UP, reboot SMP...   Problem is...  Yup, GONE!

Scenario 2:

Boot SMP again.  Compile and run Xcoral 3.1.  Pretty cool editor and
finally can do ``normal'' cut-n-paste, etc.  So I set its geometry in
.Xdefaults to =200x400.  Nope.  Will not chnge size.

I modify parse.c to have the ugly printf you see below:

        flags = XParseGeometry ( buf,  &x, &y, &width, &he
(void)fprintf(stderr, "%s.%d: x = %d, y = %d, w = %d, h =%d\n",
              __FILE__, __LINE__, x, y, width, height);

It says:

parse.c.843: x = -272640524, y = 537577259, w = 200, h = 400

(x, y are corrdinates which are unspecified, which is OK to look this
ugly)

Size is still huge (about 600x800).

So I add another printf:

        if ( (width < ((DisplayWidth ( dpy, DefaultScreen (dpy )) * 2 ) 
            || width  > DisplayWidth ( dpy, DefaultScreen (dpy ) ) )
          opt->width = (DisplayWidth ( dpy, DefaultScreen (dpy ) ) *7) /
                       10;
        else
          opt->width = width;
        
        if ( (height < ((DisplayHeight ( dpy, DefaultScreen (dpy )) * 1
            ) /5 )) 
            || height > DisplayHeight ( dpy, DefaultScreen (dpy ) ) )
          opt->height = (DisplayHeight ( dpy, DefaultScreen (dpy ) ) *
                        6) / 10;
        else
          opt->height = height;
        
(void)fprintf(stderr, "%s.%d:width = %d, height = %d\n",
              __FILE__, __LINE__, opt->width = width, opt->height);

Guess what?  The window now has the specified geometry!

I would not have paid much attention to these, unless I also had the
problem where cc1 dumps core when we run make -j8 world, some times.
Re-boot clears the crashing of the compiler.

I really am NOT a compiler person (what are you simon?  dunno...), so I
cannot intelligently proceed without some intelligent help.





If Microsoft Built Cars:

There would be an "Engine Pro" with bigger turbos, but it would be
slower on most existing roads.


Sincerely Yours, 

Simon Shapiro
Shimon@Simon-Shapiro.ORG                      Voice:   503.799.2313