Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Jun 2008 08:08:29 +0200
From:      "Riaan Kruger" <riaank@gmail.com>
To:        1@movesmountains.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Query on kgdb output
Message-ID:  <85c4b1850806052308l6a2ccd6bp2a24527b373b1ef5@mail.gmail.com>
In-Reply-To: <019b01c8c6f2$ddc7e730$f001a8c0@asgard.movesmountains.com>
References:  <019b01c8c6f2$ddc7e730$f001a8c0@asgard.movesmountains.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 5, 2008 at 11:59 AM, <1@movesmountains.com> wrote:

> Hi,
> I'm seeing regular kernel panics on my new box with a fresh install of
> 7.0-RELEASE.  I'm trying to get some information out of kgdb by following
> the instructions in the handbook - however, I'm getting a 'cannot access
> memory' message when I try it:
>
> odin2008# kgdb kernel.debug /var/crash/vmcore.1
> [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
> Undefined symbol "ps_pglobal_lookup"]
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd".
> Cannot access memory at address 0x2fd9
> (kgdb) where
> #0  0x00000000 in ?? ()
> (kgdb) quit
>
>
> Am I doing something wrong, or does this point to a hardware failure?  (I'm
> also seeing missing characters in /var/log/messages, which I addressed in a
> separate mail; not sure if it's related).
>
> Sorry the first reply went to the wrong place.
What info does a stack trace (commadn bt in kgdb) give?

Riaan



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