[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1D726098-4129-4E9E-ABA7-53B72389C70E@gmail.com>
Date: Fri, 13 Jan 2023 10:55:27 +0100
From: Jakob Koschel <jkl820.git@...il.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs/scripts/gdb: add necessary make scripts_gdb step
> On 13. Jan 2023, at 09:21, Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> 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.
> ```
I guess you are suggesting this as an alternative commit message?
I'm happy to change this in v2.
>
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
- jakob
Powered by blists - more mailing lists