From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by ozlabs.org (Postfix) with ESMTP id 9770467BA1 for ; Wed, 13 Dec 2006 17:18:26 +1100 (EST) Received: by nf-out-0910.google.com with SMTP id n15so387107nfc for ; Tue, 12 Dec 2006 22:18:24 -0800 (PST) Message-ID: Date: Wed, 13 Dec 2006 09:18:23 +0300 From: "Vitaly Wool" To: "Reeve Yang" Subject: Re: kgdb on mpc834x In-Reply-To: <198592450612121611o7f7271cbnb1404c7f7f9fda71@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_132382_29847962.1165990703798" References: <198592450612121611o7f7271cbnb1404c7f7f9fda71@mail.gmail.com> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_132382_29847962.1165990703798 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 12/13/06, Reeve Yang wrote: > > I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no > patch for 2.6.14), but gdb client cannot connec to it. I turn on all > necessary kernel hacking options. Our board is customized with > MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me > out? Following are the message from linux boot and gdb client. > You need to set up the kernel command line appropriately or add a breakpoint explicitly. Vitaly ------=_Part_132382_29847962.1165990703798 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 12/13/06, Reeve Yang <yang.reeve@gmail.com> wrote:
I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
patch for 2.6.14), but gdb client cannot connec to it. I turn on all
necessary kernel hacking options. Our board is customized with
MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
out? Following are the message from linux boot and gdb client.

You need to set up the kernel command line appropriately or add a breakpoint explicitly.

Vitaly
------=_Part_132382_29847962.1165990703798--