Subject: port-i386/6362: [dM] /dev/speaker octave-tracking goes out of range
To: None <>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: netbsd-bugs
Date: 10/26/1998 08:54:37
>Number:         6362
>Category:       port-i386
>Synopsis:       [dM] /dev/speaker octave-tracking goes out of range
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 26 06:05:00 1998
>Originator:     der Mouse
>Release:        1.3F (-current as of 1998-10-26 has same version)
	Any using $NetBSD: spkr.c,v 1.1 1998/04/15 20:26:18 drochner Exp $
	(does this mean this should be kern, rather than port-i386?)
	If octave-tracking mode is turned on, the tracking code will
	happily walk the `octave' state variable off either end of its
	allowable range, thereby accessing memory before or after the
	pitch-to-frequency array.
	and notice how the tones actually produced go weird after a
	little less than two octaves.
	Add tests in the octave-tracking code to limit `octave'.
	(I will probably write such code soon if nobody else does.
	This PR is to make sure it doesn't get forgotten.)

					der Mouse

		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B