From owner-freebsd-current@FreeBSD.ORG  Wed Nov  1 01:13:48 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A694E16A407
	for <current@freebsd.org>; Wed,  1 Nov 2006 01:13:48 +0000 (UTC)
	(envelope-from prvs=julian=453a8fdc9@elischer.org)
Received: from a50.ironport.com (a50.ironport.com [63.251.108.112])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5852F43D5F
	for <current@freebsd.org>; Wed,  1 Nov 2006 01:13:46 +0000 (GMT)
	(envelope-from prvs=julian=453a8fdc9@elischer.org)
Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229])
	by a50.ironport.com with ESMTP; 31 Oct 2006 17:13:46 -0800
Message-ID: <4547F4C9.5020902@elischer.org>
Date: Tue, 31 Oct 2006 17:13:45 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: remote gdb, kgdb and ddb
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Nov 2006 01:13:48 -0000

it's been a bew years since I did this..

some questions..

why kgdb instead of gdb -k ?

for remote, gdb seems to work fine
kgdb -r /dev/cuad0 kernel.debug   thinks it's working but seems to get 
confused a lot..

gdb with the following .gdbinit file seems to work as well.
  file kernel.debug
  set verbose 1
  set remotebreak 1
  set remotebaud 9600
  set remotedevice /dev/cuad0
  target remote /dev/cuad0

though I'm not convinced I'm seeing the last frame in which the
trap occurs. (ddb shows one  more frame).


Now that I have my machine in remote gdb, the documentation
(as sparse as it is) doesnt't say how to make the machine reboot.

from ddb I can do 'call cpu_reset' which seems to work, but
I haven't succedded in making gdb do anything similar,
nor to drop back into ddb. At one stage 'detach' used to do that
but it seems to have stopped working.


anyone have ideas (short of ipmi) on rebooting?
(the machine will be remote)
and does kgdb call gdb?  what is the relationship, and since they both 
seem to be somewhat working,  which is the right one to use?