From: Christian <evil@g-house.de>
To: linas@austin.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc32 lockups with 2.6
Date: Tue, 11 Nov 2003 01:25:41 +0100 [thread overview]
Message-ID: <3FB02C85.6090400@g-house.de> (raw)
In-Reply-To: <20031110175740.A32176@forte.austin.ibm.com>
linas@austin.ibm.com wrote:
>
> kdb is a built-in kernel debugger. gdb is useless for this case,
> although kgdb could be another alternative.
yes, i thought so. i'm still a bit confused if "kdb" and "kgdb".
as http://kgdb.sourceforge.net/whichdebugger.html points out, kdb would
be the better choice here, but i don't see any "kdb" within the kernel
config nor does it seem to be a user space-tool. anyway, i have
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SLAB=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_KGDB=y
CONFIG_KGDB_TTYS1=y
CONFIG_XMON=y
CONFIG_DEBUG_INFO=y
CONFIG_BOOTX_TEXT=y
in my kernel now (still compiling), and will try to setup kgdb tomorrow
(read: today :-))
Thank you for your time,
Christian.
--
BOFH excuse #410:
Electrical conduits in machine room are melting.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-11 0:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 20:31 ppc32 lockups with 2.6 Christian Kujau
2003-11-06 21:34 ` Christian
2003-11-10 18:50 ` linas
2003-11-10 20:32 ` Tom Rini
2003-11-10 22:39 ` Christian
2003-11-10 23:57 ` linas
2003-11-11 0:25 ` Christian [this message]
2003-11-11 15:36 ` Tom Rini
2003-11-13 0:59 ` Christian Kujau
2003-11-13 17:47 ` Tom Rini
2003-11-13 23:56 ` Christian Kujau
2003-11-14 15:57 ` Tom Rini
2003-11-18 12:33 ` Christian Kujau
2003-11-18 14:14 ` Christian Kujau
2003-11-21 15:25 ` Christian Kujau
2003-11-21 17:54 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-11-01 4:30 Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FB02C85.6090400@g-house.de \
--to=evil@g-house.de \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.