I am running MacBSD 1.0 on an SE/30 with 8 Mbytes of memory.
I have run this with both the MRG kernel and the kernel released with
1.0, and both with and without X11R6. It is much more stable and
usable than the previous releases, but I have found a few problems,
and wanted to see if anyone else has seen them. All of these problems
are uneffected by the choice of kernel or whether X is running or not.
The first is that sound doesn't work; I
don't get a beep where I would expect one, such as when a ^G is
printed.
The -C feature of xterm does not seem to work; it will not
transfer the console output to an xterm. This does not seem to have
anything to do with permissions on /dev/console; I have set this to
777 with the same results. The console output always goes to the
screen as a whole, not to a window.
The GDB that came with the system does not seem to work
correctly. Consider the following transcript of a debugging session
for a very simple program:
myname.my.domain% gdb vartest
(gdb) list
1 main(argc, argv)
2 int argc;
3 char *argv[];
4 {
5 int x;
6
7 x = 1;
8 x = 2;
9 }
(gdb) n
The program is not being run.
(gdb) b main
Breakpoint 1 at 0x26de: file vartest.c, line 7.
(gdb) n
The program is not being run.
(gdb) r
Starting program: /home/giering/test/vartest
Breakpoint 1, main (argc=1, argv=0xffffc6ec) at vartest.c:7
7 x = 1;
(gdb) n
8 x = 2;
(gdb) p x
$1 = 1
(gdb) p x
$2 = 808483960
(gdb) n
9 }
(gdb) p x
$3 = 808483960
(gdb) quit
The program is running. Quit anyway (and kill it)? (y or n) y
myname.my.domain%
The problem is that the variable x can only be printed once. After
that, p always reports the same arbitrary value, whatever the value of
x.
I also have had problems with the compiler, specifically
trying to compile TeX. I haven't narrowed these down to the point
where I can say much about them, however.
Does any of this sound familiar?
Ted Giering