Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Sep 2002 22:00:33 +0200
From:      Hanspeter Roth <hanspeter_roth@hotmail.com>
To:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: interrupting the remote kernel
Message-ID:  <20020906220033.A1830@gicco.cablecom.ch>
In-Reply-To: <Pine.BSF.4.21.0209061210460.39088-100000@InterJet.elischer.org>; from julian@elischer.org on Fri, Sep 06, 2002 at 12:11:28PM -0700
References:  <20020906204324.A1258@gicco.cablecom.ch> <Pine.BSF.4.21.0209061210460.39088-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
  On Sep 06 at 12:11, Julian Elischer spoke:

> hit CTL_ALT_ESC on it's keyboard...

Doing this on the remote host (running gdb) tells me `No debugger in
kernel'.
Doing this on the target host passes control to the remote gdb.

But I want to pass control to the remote debugger by issuing
the interrupt command on the _remote_ host (in gdb).

> or do:
> sysctl debug.enter_debugger=gdb

Doing this on the target host also passes control to the remote
gdb.

But I want to be able to pass control to the debugger when the
target kernel `hangs', that is when no `ctl-alt-f1', `ctl-alt-del'
has any effect.

I thought that remotebreak on the remote gdb should allow me this.
But it seems to be something else...

-Hanspeter

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020906220033.A1830>