Yeah, but what you got this time wasn't the Mac's debugger...

Cmnd-Power is used to generate a NMI (Non-Maskable Interrupt).  When
you're running vanilla MacOS, the interrupt vector for NMI is pointed to
the mini-debugger in the Mac ROMs, and you get a dialog box on the screen
with just a ">" prompt character.  If you're running MacsBug with your
MacOS, then you get into that debugger instead.

Now, when you're running NetBSD/Mac, the vector points to the gdb debugger
built into just about all of the publicly distributed kernels.  gdb won't
ever show up under MacOS, and MacsBugs won't ever show up under MacBSD.

BTW, for MacsBug, the "Macs" part has nothing to do with Macintosh - MACS
is an acronym for Motorola Advanced Computer System!  The original MacsBug
code was developed by Motorola, and modified by Apple to work in the MacOS
environment!

On Thu, 2 Jan 1997, Jamie Le Tual wrote:

> 
> actually, cmd-power envokes the macintosh built-in debugger. very rarely 
> documented to exist at all, and getting a list of commands is harder. But 
> to get back to where you came from, type 'G <return>' 
> 
>  ____________________________________________________________________
> |                                     | Any opinions expressed are   |
> |  j_letua@alcor.concordia.ca         | those of my other personality|
> |  http://alcor.concordia.ca/~j_letua |        and no one else!      |
> |_____________________________________|______________________________|
> 
> On Wed, 1 Jan 1997, Richard Ervin wrote:
> 
> > On the Duo230 again:
> > 
> > I installed Macsbug
> > 
> > After the adb: cleanup: nothing returned messages, I pressed cmnd-<power>
> > (I guessed at the combination!) and got the following result:
> > 
> > Panic Switch: PC is 0x96562
> > Stopped at      _Debugger+0x6:  unlk     a6
> > db>
> > 
> > (Is this Macsbug?) At this point, the keyboard is useless.
> --snip--
> > Thanks,
> > Rich
> > 
>