[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46890F8D.3080807@windriver.com>
Date: Mon, 02 Jul 2007 09:45:33 -0500
From: Jason Wessel <jason.wessel@...driver.com>
To: Sergei Shtylyov <sshtylyov@...mvista.com>
CC: kgdb-bugreport@...ts.sourceforge.net,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
Andrew Morton <akpm@...ux-foundation.org>, paulus@...ba.org,
linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.22-rc6-mm1
Sergei Shtylyov wrote:
> Hello.
>
> Jason Wessel wrote:
>
>>>> allmodconfig on powerpc (iMac g3) fails due to
>>>> git-kgdb.patch. allmodconfig defaults should be changed?
>
>>>> CC arch/powerpc/kernel/kgdb.o
>>>> arch/powerpc/kernel/kgdb.c:485:2: error: #error Both XMON and KGDB
>>>> selected in .config. Unselect one of them.
>>>> make[1]: *** [arch/powerpc/kernel/kgdb.o] Blad 1
>>>> make: *** [arch/powerpc/kernel] Blad 2
>
> This patch does not seem complete as the #error that was tiggering
> has not been deleleted from arch/powerpc/kernel/kgdb.c (and not it's
> useless)
>
I suppose the argument could be made to remove the check in the compiled
file, but it does serve as a way to protect kgdb for now if someone
tries to hard compile in xmon and kgdb. Completely unpredictable
results will occur with the debugger unless some pieces are fixed. I
would rather make sure until that happens there is no way head down the
rat hole.
That issue aside would it be useful to have xmon+kgdb? After having
looked at the hook points for xmon, if a command was added to xmon to
provide an "detach" it would be easy enough to have kgdb and xmon in the
same kernel. Obviously only one or the other can be used at any given time.
Jason.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists