<div dir="ltr">Hello all,<br>
<br>As the title says, any of you have successfully tried to debug Linux<br>4.13 with <span class="gmail-il">QEMU</span>? My problem is that it is not possible to break (even<br>with hbreak) in any function of the kernel, from the most used<br>(schedule or spin_lock) to the most obvious (uptime_proc_show when<br>/proc/uptime is read).<br>
<br>To be more specific, <span class="gmail-il">QEMU</span> correctly stops if I put "-s -S" on the<br>command line, and perfectly continue the execution of the kernel when<br>I connect gdb using 'target remote :1234'. However, any breakpoint is<br>simply ignored.<br>
<br>I have followed any possible tutorial and any possible answer to<br>similar user questions. I also tried to do the same on a 16.04 version<br>of Ubuntu, but the result is always the same. In particular, I have<br>followed <a href="https://stackoverflow.com/questions/11408041/how-to-debug-the-linux-kernel-with-gdb-and-qemu" rel="noreferrer" target="_blank">https://stackoverflow.com/<wbr>questions/11408041/how-to-<wbr>debug-the-linux-kernel-with-<wbr>gdb-and-<span class="gmail-il">qemu</span></a>,<br>using both a busybox image and a raw filesystem image of Archlinux.<br>
<br>There is any known problem in debugging Linux? How can I "debug" this<br>debug process?<br>
<br>Thank you!<br clear="all"><br>-- <br><div class="gmail_signature">Stay open, be free.</div>
</div>