From: Benjamin ZORES <benjamin.zores@alcatel-lucent.fr>
To: linuxppc-dev@ozlabs.org
Subject: Linux 2.6.23-rc7 kGDB broken
Date: Tue, 25 Sep 2007 09:41:33 +0200 [thread overview]
Message-ID: <46F8BBAD.30008@alcatel-lucent.fr> (raw)
Hi,
I used to use linux-2.6-kgdb git tree from jwessel to extract kGDB
related patches
but I now have seen that it has been included in -mm branch.
However, in this branch, kGDB seems to be broken at least on PowerPC
(see http://lkml.org/lkml/2007/9/19/103).
It seems to me that the only reason is due to a missing header file
in include/asm-powerpc/kgdb.h
This file used to be present in kgdb tree (see
http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=blob_plain;f=include/asm-powerpc/kgdb.h;hb=kgdb_2.6.22-rc6)
but is no longer part of the patch.
Is there any reason for that ?
By opposition to what could be said in first LKML thread, adding this
file is enough to restore kGDB on PowerPC.
I've tested it and it compiles (and work) just fine (and as expected).
Can this file be restored ?
Ben
reply other threads:[~2007-09-25 8:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46F8BBAD.30008@alcatel-lucent.fr \
--to=benjamin.zores@alcatel-lucent.fr \
--cc=linuxppc-dev@ozlabs.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.