Am Mo, 2002-05-27 um 19.52 schrieb David O'Brien:
> On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote:
> > Please read bin/38236. I wasn't asking for general directions but for a
> > specific solution to a current -current problem.
>
> RTFM specifically the "-gstabs+" GCC optio
On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote:
> Please read bin/38236. I wasn't asking for general directions but for a
> specific solution to a current -current problem.
RTFM specifically the "-gstabs+" GCC option.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
Am Sa, 2002-05-25 um 02.30 schrieb Craig Carey:
> [...]
> savecore(8) should copy a dump of the crashed kernel to /var/crash and
> created files kernel.0 and vmcore.0.
>
> gdb -k kernel.0 vmcore.0
>
hunter[13]$ gdb -k kernel.debug vmcore.19
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free
At 02\05\24 14:52 +0200 Friday, Georg-W. Koltermann wrote:
>Hi,
>
>I got a couple of kernel panics recently, some of them "buffer not
>locked". I would like to know how I can get more information out of the
>dump.
>
>The system's gdb does not like the dump format any more, see also
>bin/38
Hi,
I got a couple of kernel panics recently, some of them "buffer not
locked". I would like to know how I can get more information out of the
dump.
The system's gdb does not like the dump format any more, see also
bin/38236. There is an advertised workaround in that pr of using gdb52,
but I co
