Raymond Wiker <Raymond.Wiker@...> writes:
> Christophe Rhodes writes:
> > On the only MacOS machine I have access to, I can't reproduce this;
> > Brian Mastenbrook suggests that this might be because it's a dual
> > processor machine.
> I did this on my 867 MHz PB12, and saw this behaviour when I
> tried to build the contrib stuff. I have some other local
> modifications, though, taken from Brian Mastenbrook's web page (the
> one with the instructions for building SBCL under Panther and on G5s).
> It seemed that I got a breakpoint every time run-program was
> called from make-target-contrib (3 times?)
> I also tried provoking this by calling run-program from the
> REPL, and eventually managed to wedge SBCL (the test was something
> like "echo hello, world").
Well, with the new, more correct RECEIVE-PENDING-INTERRUPT
implementation, what *should* be happening is that the system should
indeed get a SIGTRAP, get into sigtrap_handler (in
src/runtime/ppc-arch.c), and execute the trap_PendingInterrupt case in
the switch statement: move the PC forward over the current
instruction, handle the pending interrupt, and resume execution.
What's actually happening, I don't know. gdb is the enemy of your
enemy, I'm afraid.
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)