From: Tom Rini <trini@kernel.crashing.org>
To: Christian Kujau <evil@g-house.de>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: still unable to compile with kgdb enabled
Date: Fri, 9 Apr 2004 15:06:46 -0700 [thread overview]
Message-ID: <20040409220646.GB1787@smtp.west.cox.net> (raw)
In-Reply-To: <40771841.8040001@g-house.de>
On Fri, Apr 09, 2004 at 11:40:17PM +0200, Christian Kujau wrote:
> hi,
>
> happily compiling kernels from 2.5 to 2.6 i finally wanted to give KGDB
> a try as suggested often enough. but i fail to do this.
[snip]
> i was looking for a kgdb patch on kgdb.sourceforge.net, but the latest
> version there is KGDB 2.0.1-2.0.5, which is for linux-2.6.1 only. on
> http://spop.free.fr/kgdb/ i found a kgdb-1.9-for-2.4.25.patch.bz2,
> applying cleanly, but still gives me errors and does not compile:
The CVS version of the patch is against 2.6.5, and if you only pass in
'kgdbwait', it should work w/o mods (otherwise it breaks in very early,
and requires some additional work). I've tested this out on a few
machines locally, but not PPC_MULTIARCH, so there might be a few
incidental things required to be fixed. I've been using the KGDB_8250,
and not PPC_SIMPLE_SERIAL, but I plan on testing that sometime in the
future.
FWIW, I'm about to go off for 2 weeks vacation, so I probably won't be
able to help you, if it doesn't work right away.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-09 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 21:40 still unable to compile with kgdb enabled Christian Kujau
2004-04-09 22:06 ` Tom Rini [this message]
2004-04-10 15:15 ` 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=20040409220646.GB1787@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=evil@g-house.de \
--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.