From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Any successful story of debugging linux 4.13 with qemu 2.10 and gdb 8.01?
Date: Thu, 21 Sep 2017 11:01:05 +0200 [thread overview]
Message-ID: <20170921090105.GA8394@kroah.com> (raw)
In-Reply-To: <CAOhBGduwycQZvzw3BfE3_snpa35fGHsbwTcfCjwptAGxRTKftQ@mail.gmail.com>
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
next prev parent reply other threads:[~2017-09-21 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 8:18 Any successful story of debugging linux 4.13 with qemu 2.10 and gdb 8.01? jjDaNiMoTh
2017-09-20 15:20 ` 慕冬亮
2017-09-20 19:29 ` jjDaNiMoTh
2017-09-21 7:21 ` Greg KH
2017-09-21 7:29 ` Saket Sinha
2017-09-21 8:43 ` jjDaNiMoTh
2017-09-21 9:01 ` Greg KH [this message]
2017-09-21 17:08 ` 慕冬亮
2017-09-22 6:09 ` Saket Sinha
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=20170921090105.GA8394@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.