From owner-freebsd-current  Sun May 17 10:45:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA17871
          for freebsd-current-outgoing; Sun, 17 May 1998 10:45:27 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17852
          for <current@FreeBSD.ORG>; Sun, 17 May 1998 10:45:22 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA08122;
	Mon, 18 May 1998 03:44:36 +1000
Date: Mon, 18 May 1998 03:44:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199805171744.DAA08122@godzilla.zeta.org.au>
To: pst@juniper.net, regnauld@deepo.prosa.dk
Subject: Re: Serial console, system hangs and DDB...
Cc: current@FreeBSD.ORG, julian@whistle.com, scrappy@hub.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>There already is such a thing -- it's called "BREAK_TO_DEBUGGER".
>
>You need to send a <break> indication down the serial line to the target
>machine.  The ~# that you're probably sending to your solaris machines
>is actually getting translated by tip(1) into a break signal.

It is fairly broken, however.  It only works if interrupts are enabled
on the serial port for the console, and interrupts are only enabled if
a process (e.g., getty or a shell) has the console open.  This makes
it useless for debugging bootstraps, reboots, and serial ports with
broken interrupts.

Bruce

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