From: "Linas Vepstas (Code Aurora)" <linas@codeaurora.org>
To: Dongdong Deng <libfetion@gmail.com>
Cc: Richard Kuo <rkuo@codeaurora.org>,
linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 31/36] Hexagon: kgdb support files
Date: Mon, 19 Sep 2011 10:15:32 -0500 [thread overview]
Message-ID: <20110919151532.GA6830@codeaurora.org> (raw)
In-Reply-To: <CAGn38=0herzUuFyq7-4irgi8Myq0tibz0FGLiZY0GRq8iiO5kg@mail.gmail.com>
On Mon, Sep 19, 2011 at 05:46:09PM +0800, Dongdong Deng wrote:
> On Thu, Sep 15, 2011 at 2:19 AM, Richard Kuo <rkuo@codeaurora.org> wrote:
> > +#if 0
> > + ret = kgdb_handle_exception(args->trapnr & 0xff, args->signr, args->err,
> > + regs);
> > + if (ret)
> > + return NOTIFY_DONE;
> > +#endif
>
> Hmm, the key code of invoking kgdb_core was disabled by "#if 0".
The Hexagon kgdb implementation is incomplete; I work on it as time
permits and urgency requires. I know from direct experience that,
for kernel bringup and stress testing on new platforms, that kdb is
invaluable, being infinitely easier to use than any hardware debugger.
(cheaper, too)
This world could use a really cheap, easy-to-setup jtag debugger.
-- Linas
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-09-19 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 18:19 [PATCH v4 31/36] Hexagon: kgdb support files Richard Kuo
2011-09-14 18:19 ` Richard Kuo
2011-09-19 9:46 ` Dongdong Deng
2011-09-19 9:46 ` Dongdong Deng
2011-09-19 15:15 ` Linas Vepstas (Code Aurora) [this message]
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=20110919151532.GA6830@codeaurora.org \
--to=linas@codeaurora.org \
--cc=libfetion@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).