Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-04 Thread Warner Losh
On Mon, May 3, 2021 at 12:38 AM bob prohaska wrote: > After a successful compile of audio/xoscope on a Pi4 running current a > stream of messages appeared on the console and in the security log > while xoscope was running: > > > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl

Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-03 Thread Mark Millard via freebsd-ports
On 2021-May-3, at 08:23, bob prohaska wrote: > On Mon, May 03, 2021 at 01:00:03AM -0700, Mark Millard via freebsd-ports > wrote: > [detailed code tour omitted] > >> >> My guess would be xoscope used a signed 32-bit type >> that got a value with sign extension to 64 bits >> before the value

Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-03 Thread bob prohaska
On Mon, May 03, 2021 at 01:00:03AM -0700, Mark Millard via freebsd-ports wrote: [detailed code tour omitted] > > My guess would be xoscope used a signed 32-bit type > that got a value with sign extension to 64 bits > before the value started being treated as unsigned. > If it had used an

Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-03 Thread Mark Millard via freebsd-ports
On 2021-May-2, at 23:37, bob prohaska wrote: > After a successful compile of audio/xoscope on a Pi4 running current a > stream of messages appeared on the console and in the security log > while xoscope was running: > > > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl