All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jakob Koschel <jkl820.git@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/scripts/gdb: add necessary make scripts_gdb step
Date: Fri, 13 Jan 2023 15:21:12 +0700	[thread overview]
Message-ID: <Y8EUeB8tbpNVcn71@debian.me> (raw)
In-Reply-To: <20230112-documentation-gdb-v1-1-09ab556e9124@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

On Thu, Jan 12, 2023 at 05:09:25PM +0100, Jakob Koschel wrote:
> In order to debug the kernel successfully with gdb you need to run
> 'make scripts_gdb' nowadays.
> 
> This was changed with the following commit:
> 
> Commit 67274c083438340ad16c ("scripts/gdb: delay generation of gdb
> constants.py")
> 
> In order to have a complete guide for beginners this remark
> should be added to the offial documentation.
> 

What about below?

```
Since commit <commit>, debugging kernel requires gdb scripts to be built
with "make scripts_gdb" first. Reflect this requirement in the
"Debugging kernel and modules via gdb" documentation.
```

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-01-13  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 16:09 [PATCH] docs/scripts/gdb: add necessary make scripts_gdb step Jakob Koschel
2023-01-13  8:21 ` Bagas Sanjaya [this message]
2023-01-13  9:55   ` Jakob Koschel
2023-01-19 21:09 ` Jonathan Corbet

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=Y8EUeB8tbpNVcn71@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jkl820.git@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.