Re: misc/56223: Compilation as root for various pkgsrc packages screws up the console

["David H. Gutteridge" <david%gutteridge.ca@localhost>]

The following reply was made to PR misc/56223; it has been noted by GNATS.

From: "David H. Gutteridge" <david%gutteridge.ca@localhost>
To: gnats-bugs%netbsd.org@localhost, dholland-bugs%netbsd.org@localhost
Cc: 
Subject: Re: misc/56223: Compilation as root for various pkgsrc packages
 screws up the console
Date: Fri, 04 Jun 2021 13:17:11 -0400

 On Fri, 4 Jun 2021 at 16:35:02 +0000 (UTC), David Holland wrote:
   >On Mon, May 31, 2021 at 09:25:00PM +0000, davshao%gmail.com@localhost 
 wrote:
   > > When in console as root on various machines, such as one with an
   > > Intel Ivy Bridge integrated graphics or one with a CAICO AMD Radeon
   > > graphics card, simply doing something like
   > >
   > > cd /usr/pkgsrc/pkgtools/cwrappers
   > > make clean && make replace package clean
   > > cd /usr/pkgsrc/pkgtools/digest
   > > make clean && make replace package clean
   > > cd /usr/pkgsrc/devel/gmake
   > > make clean && make replace package clean
   > >
   > > in the make portion of gmake causes characters to stop being
   > > displayed on the console.  This is not observed if building in
   > > native or modular xorg or building while ssh-ing.  The command
   > > appears to finish.
   >
   >(a) [you know this] don't build as root (though if it's specific to
   >being root vs. just being on the console that would be interesting
   >info)
 
   I'm able to reproduce this on a machine running -current with Ivy 
 Bridge
   graphics (but not on a machine running 9.2 with Radeon Kaveri). It
   doesn't relate to running as root, it's reproducible as any user.
 
   >(b) is it not displaying or is the console wedged? e.g. after it
   >finishes, if you type ^G, does it beep? can you start other commands
   >by typing blind?
 
   For me, it simply isn't displaying. It's not wedged, it will still
   accept and run commands, it's just the display is lost. Typing "exit"
   gets me back to a visible login prompt.
 
   >(c) is it repeatable and is there a specific package it's linked to,
   >or is it e.g. the result of scrolling a lot or too quickly? Might be
   >interesting to check if e.g. uuencode /netbsd /netbsd and letting that
   >scroll triggers it.
 
   It's reproducible for me by building anything that causes GCC to use
   particular escape codes for formatting warning messages. E.g., it's
   easily reproducible by typing "make package" in x11/xscreensaver. It is
   also reproducible by capturing the output of one of those builds using
   script(1), then using cat(1) to display it on the console. When it hits
   particular escape codes, the display goes blank.
 
   Dave