From owner-freebsd-hackers  Mon Apr 28 21:43:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA23892
          for hackers-outgoing; Mon, 28 Apr 1997 21:43:07 -0700 (PDT)
Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA23875
          for <freebsd-hackers@freebsd.org>; Mon, 28 Apr 1997 21:42:55 -0700 (PDT)
Received: (qmail 4721 invoked by uid 1000); 29 Apr 1997 04:21:10 -0000
Message-ID: <XFMail.970428212110.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
In-Reply-To: <3364E6BB.41C67EA6@whistle.com>
Date: Mon, 28 Apr 1997 20:33:46 -0700 (PDT)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Julian Elischer <julian@whistle.com>
Subject: Re: A Desparate Plea for Help...
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi Julian Elischer;  On 28-Apr-97 you wrote: 

...

> The best thing for you to do with this
> is to compile the gernet
                    ^^^^^^ Kernel.  Right?
> using -g
> do this by using 
> config -g
> do: (on the compile machine)
> make
> cp kernel kernel.debug
> strip -d kernel

Are the two above in / or in /usr/src/sys/compile/WHATEVER?
> 
> also:
> cat >.gdbinit <<DONE
> set remotebaud 9600
> file kernel.debug
> target remote  /dev/cuaa1
> DONE

In / or in /usr/src/sys/compile/WHATEVER?
> 
> 
> compile the options DDB and set the default 
> debugger to be gdb by booting with -g
> 
> then if you get a crash,
> make sure that /dev/cuaa1 (com2) on your source machine is
> connected to com1 on the victim machine 
> and type 
> cd /sys/compile/<MYKENREL>
> gdb
> 
> this (due to the .gdbinit) will fire up gdb and allow you to walk up and
> down the 
> stack trace of the crashed kernel.
> 
> even if the screen is stuck in X11.
> 
> there are some problems I've seen.
> 
> 1/ the newest gdb versions are not as good at doing this as some of the
> older ones.

What is an ``older but better'' one?  Version #, etc...

> and sometimes get confused.
> 2/ you must remember to make sure the system has sert gdb to be the
> kernel debugger.
> (there may be a compile time option for this.. I forget)

Could not find that, other than the -g at boot time.

> 3/ some uarts don't like this if com1 is already being used for
> something..
> (move your mouse to com2)

ay suggestion on what are the best settings for com4?  I need a mouse, a
serial
port for modem and a serial port for ISDN.  Can I configure everything to
use
com4 instead of com1?  Will make it simpler here.

Simon