linux-kernel - Re: KGDB fails to pass selft tests on x86-64 (v2.6.26)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <488891F2.9020509@windriver.com>
Date:	Thu, 24 Jul 2008 09:30:10 -0500
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Francis Moreau <francis.moro@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: KGDB fails to pass selft tests on x86-64 (v2.6.26)

Francis Moreau wrote:
> On Thu, Jul 24, 2008 at 3:24 PM, Francis Moreau <francis.moro@...il.com> wrote:
>   
>> I wanted to give kgdb a try on a v2.6.26 kernel. My cpu is an
>> x86-64.
>>
>> So the first thing I did is to enable kgdb support and also the
>> kgdb self tests:
>>
>> CONFIG_HAVE_ARCH_KGDB=y
>> CONFIG_KGDB=y
>> CONFIG_KGDB_SERIAL_CONSOLE=y
>> CONFIG_KGDB_TESTS=y
>> # CONFIG_KGDB_TESTS_ON_BOOT is not set
>>
>> Once compiled I booted this kernel through qemu and got the following:
>>
>>     
>
> and unfortunately it seems this issue is related to qemu: if I did boot the
> kernel without qemu and the self tests passed...
>
>
>   

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.

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.

Cheers,
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/