From: Jason Wessel <jason.wessel@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: tglx@linutronix.de, a.beregalov@gmail.com,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: kgdb test suite failure
Date: Tue, 27 May 2008 20:43:17 -0500 [thread overview]
Message-ID: <483CB8B5.2040702@windriver.com> (raw)
In-Reply-To: <20080523.000129.193706282.davem@davemloft.net>
David Miller wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Thu, 22 May 2008 23:14:23 +0200 (CEST)
>
>> Please use HW breakpoints in the test suite. The RFC patch looks
>> horrible :)
>
> ftrace needs basically the same kind of facility as kgdb
> needs here. So bypassing the need for kgdb won't get around
> the problem in general.
It does seem like there should be a general way to force a controlled
write to a read-only page. That would certainly allow for the use of
software breakpoints with KGDB. At the point in time that such calls
come into existence I would certainly consider adding a toggle which
you can use from the debugger to provide such access.
At least for the current time for kgdb, we will use hardware
breakpoints.
Jason.
next prev parent reply other threads:[~2008-05-28 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 14:14 kgdb test suite failure Alexander Beregalov
2008-05-11 19:32 ` Rafael J. Wysocki
2008-05-20 15:18 ` Jason Wessel
2008-05-20 18:30 ` Alexander Beregalov
2008-05-21 16:27 ` Jason Wessel
2008-05-22 21:14 ` Thomas Gleixner
2008-05-23 7:01 ` David Miller
2008-05-28 1:43 ` Jason Wessel [this message]
2008-05-28 1:37 ` Jason Wessel
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=483CB8B5.2040702@windriver.com \
--to=jason.wessel@windriver.com \
--cc=a.beregalov@gmail.com \
--cc=davem@davemloft.net \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.