From: "Francis Moreau" <francis.moro@gmail.com>
To: "Jason Wessel" <jason.wessel@windriver.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: KGDB fails to pass selft tests on x86-64 (v2.6.26)
Date: Thu, 24 Jul 2008 17:19:52 +0200 [thread overview]
Message-ID: <38b2ab8a0807240819s48a233a0xb73e0da4c732020e@mail.gmail.com> (raw)
In-Reply-To: <488891F2.9020509@windriver.com>
Hello,
On Thu, Jul 24, 2008 at 4:30 PM, Jason Wessel
<jason.wessel@windriver.com> wrote:
>
> It is because the qemu you are using does not support hardware
> breakpoints. The tests will warn, but the kernel will continue to boot
> and tell you that hw breakpoint support doesn't work on your simulated
> hardware.
ah ok, thanks.
While I have your attention, I sometimes (well pretty often actually) got this
inside my gdb session:
(gdb) n
warning: Invalid remote reply: 00
or
(gdb) n
warning: Invalid remote reply: 00
warning: Invalid remote reply:
c0dcb40f0081ffff08e59f0f0081ffff00b1a40f0081ffff8086400f0081ffff704e2c81ffffffff01000000008000000d00000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000ffffffffffffffff0000000000000000
Do you any idea what's wrong in this case ?
>
> Also, if you plan to use software breakpoints, please make sure to turn
> off CONFIG_DEBUG_RODATA, else they will not work. This is a regression
> which will is on my list of things to take a look at, as time permits.
>
Yes I did that since I did notice a previous post where you adviced the same
thing.
Thanks
--
Francis
prev parent reply other threads:[~2008-07-24 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 13:24 KGDB fails to pass selft tests on x86-64 (v2.6.26) Francis Moreau
2008-07-24 14:08 ` Francis Moreau
2008-07-24 14:30 ` Jason Wessel
2008-07-24 14:38 ` Vegard Nossum
2008-07-24 14:55 ` Jason Wessel
2008-07-24 19:05 ` Vegard Nossum
2008-07-24 15:19 ` Francis Moreau [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=38b2ab8a0807240819s48a233a0xb73e0da4c732020e@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.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