On Jul 5, 2014, at 1:33 PM, John-Mark Gurney wrote:
> Peter Jeremy wrote this message on Fri, Jul 04, 2014 at 21:27 +1000:
>> On 2014-Jul-04 02:28:48 -0700, John-Mark Gurney wrote:
>>> So, I recently tried to break into the debugger w/ the various key
>>> sequences that I know about, and none o
Peter Jeremy wrote this message on Fri, Jul 04, 2014 at 21:27 +1000:
> On 2014-Jul-04 02:28:48 -0700, John-Mark Gurney wrote:
> >So, I recently tried to break into the debugger w/ the various key
> >sequences that I know about, and none of them worked... I've tried
> >CTRL-ESC, ALT-ESC, CTRL-ALT-E
On 2014-Jul-04 02:28:48 -0700, John-Mark Gurney wrote:
>So, I recently tried to break into the debugger w/ the various key
>sequences that I know about, and none of them worked... I've tried
>CTRL-ESC, ALT-ESC, CTRL-ALT-ESC, CTRL-PRTSCR, ALT-PRTSCR and
>CTRL-ALT-PRTSCR, and many other different on
On Fri, 4 Jul 2014 02:28-0700, John-Mark Gurney wrote:
> So, I recently tried to break into the debugger w/ the various key
> sequences that I know about, and none of them worked... I've tried
> CTRL-ESC, ALT-ESC, CTRL-ALT-ESC, CTRL-PRTSCR, ALT-PRTSCR and
> CTRL-ALT-PRTSCR, and many other differen
So, I recently tried to break into the debugger w/ the various key
sequences that I know about, and none of them worked... I've tried
CTRL-ESC, ALT-ESC, CTRL-ALT-ESC, CTRL-PRTSCR, ALT-PRTSCR and
CTRL-ALT-PRTSCR, and many other different ones... I've verified that
I can sysctl debug.kdb.enter=1 to