upstream/0.3.7/BUGS

$Id: BUGS,v 1.37 2005/11/13 12:34:02 debug Exp $

Hm. This file is pretty old. Some of these are still valid, though.

===================================================================

  x)  An unknown math coprocessor bug. (Ultrix' dxclock sometimes looks
      weird.)

  x)  Enabling cache emulation (./configure --enable-caches) triggers bugs.

  x)  Linux/DECstation (Debian) oopses extremely often unless -U is used
      at run-time. I'm not sure yet why it bugs out. With -U, the risk is
      lower, but not completely gone. _Maybe_ this is a bug in Linux. Why?
      Because the oops message contains things like ANSI escape codes and
      characters in registers (including the pc and return address register);
      this looks like a buffer overflow in the serial driver. (Another thing
      that gives weight to this theory is that the serial driver in Linux is
      still being developed.)  But this is just a guess.

  o)  Hardware device ticks are done at cycle specific intervals, not
      instruction intervals, so sometimes a fraction of a cycle can be
      "lost".

  o)  Running Linux/DECstation 2.4.26 with no scsi disks attached causes
      a warning message to be printed by Linux.

  o)  UDP packets that are too large are not handled well by the Lance device.

  o)  Colors in X11 framebuffers on MacOS X hosts are wrong. (I'm not sure
      how to solve this; the code works on both little-endian (Alpha) and
      big-endian (UltraSPARC) X-servers...)

  o)  Binary-translated 64-bit stuff checks to see if the top 32 bits are
      all zeroes or all ones, and then uses 32-bit tables and such. This
      is a bug. It should check the top 33 bits, not 32. (Alpha only, already
      fixed for i386?)

  o)  NetBSD/arc 2.0 uses the ASC controller in a way which GXemul cannot yet
      handle. (NetBSD 1.6.2 works ok.)

1	$Id: BUGS,v 1.37 2005/11/13 12:34:02 debug Exp $
2
3	Hm. This file is pretty old. Some of these are still valid, though.
4
5	===================================================================
6
7	x) An unknown math coprocessor bug. (Ultrix' dxclock sometimes looks
8	weird.)
9
10	x) Enabling cache emulation (./configure --enable-caches) triggers bugs.
11
12	x) Linux/DECstation (Debian) oopses extremely often unless -U is used
13	at run-time. I'm not sure yet why it bugs out. With -U, the risk is
14	lower, but not completely gone. _Maybe_ this is a bug in Linux. Why?
15	Because the oops message contains things like ANSI escape codes and
16	characters in registers (including the pc and return address register);
17	this looks like a buffer overflow in the serial driver. (Another thing
18	that gives weight to this theory is that the serial driver in Linux is
19	still being developed.) But this is just a guess.
20
21	o) Hardware device ticks are done at cycle specific intervals, not
22	instruction intervals, so sometimes a fraction of a cycle can be
23	"lost".
24
25	o) Running Linux/DECstation 2.4.26 with no scsi disks attached causes
26	a warning message to be printed by Linux.
27
28	o) UDP packets that are too large are not handled well by the Lance device.
29
30	o) Colors in X11 framebuffers on MacOS X hosts are wrong. (I'm not sure
31	how to solve this; the code works on both little-endian (Alpha) and
32	big-endian (UltraSPARC) X-servers...)
33
34	o) Binary-translated 64-bit stuff checks to see if the top 32 bits are
35	all zeroes or all ones, and then uses 32-bit tables and such. This
36	is a bug. It should check the top 33 bits, not 32. (Alpha only, already
37	fixed for i386?)
38
39	o) NetBSD/arc 2.0 uses the ASC controller in a way which GXemul cannot yet
40	handle. (NetBSD 1.6.2 works ok.)
41