<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-09-21 9:21 GMT+02:00 Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com" target="_blank">greg@kroah.com</a>></span>:<span class="gmail-"></span><br><span class="gmail-"></span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
</span>Why do you think that it requires developers to use a debugger and qemu<br>
to test their code? I've never used a debugger on the kernel in all of<br>
my years of kernel development...<br><br></blockquote><div><br></div><div>I imagined that, at least in early development phases, developers can benefit</div><div> from the use of a debugger, but it seems that I was wrong. Of course, for</div><div> newbies like me, a debugger is essential to understand flow and relations</div><div> between kernel code, and I'm happy that this solution is already in the</div><div> documentation (unfortunately, not for the version I was using, 4.13). Maybe the</div><div> patch pointed out by Saket can be backported to releases which have the</div><div> possibility to enable KALSR, such as 4.9 (LTS) and 4.13 itself (stable)?<br><br>[1] <a href="https://www.kernel.org/doc/html/v4.13/dev-tools/gdb-kernel-debugging.html">https://www.kernel.org/doc/html/v4.13/dev-tools/gdb-kernel-debugging.html</a></div><div><br></div><div>JJD<br></div></div><br clear="all"><br>-- <br><div class="gmail_signature">Stay open, be free.</div>
</div></div>