From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Thu, 21 Sep 2017 11:01:05 +0200
Subject: Any successful story of debugging linux 4.13 with qemu 2.10 and
	gdb 8.01?
In-Reply-To: <CAOhBGduwycQZvzw3BfE3_snpa35fGHsbwTcfCjwptAGxRTKftQ@mail.gmail.com>
References: <CAOhBGduWQBM0X3y-hQrtPHV_diFdqVUy3V2XnW-F=8CQqquZAw@mail.gmail.com>
	<CAD-N9QWqxffUUosAai4K8m77G35XwXn1kuWnoF_exT2vPudrvw@mail.gmail.com>
	<20170920192917.lg33kitgd4tqh4bx@judith.localdomain>
	<20170921072143.GA4588@kroah.com>
	<CAOhBGduwycQZvzw3BfE3_snpa35fGHsbwTcfCjwptAGxRTKftQ@mail.gmail.com>
Message-ID: <20170921090105.GA8394@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Thu, Sep 21, 2017 at 10:43:08AM +0200, jjDaNiMoTh wrote:
> 
> 
> 2017-09-21 9:21 GMT+02:00 Greg KH <greg@kroah.com>:
> 
>    
>     Why do you think that it requires developers to use a debugger and qemu
>     to test their code?? I've never used a debugger on the kernel in all of
>     my years of kernel development...
> 
> 
> 
> I imagined that, at least in early development phases, developers can benefit
> from the use of a debugger, but it seems that I was wrong. Of course, for
> newbies like me, a debugger is essential to understand flow and relations
> between kernel code, and I'm happy that this solution is already in the
> documentation (unfortunately, not for the version I was using, 4.13). Maybe the
> patch pointed out by Saket can be backported to releases which have the
> possibility to enable KALSR, such as 4.9 (LTS) and 4.13 itself (stable)?

Sure, you can request it, look at the documentation here for how to do
that:

    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html