From: Florian Fainelli <f.fainelli@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: No care given to GDB scripts..
Date: Wed, 29 Nov 2023 14:48:02 -0800 [thread overview]
Message-ID: <cfc3aa17-0f1b-4ffc-b848-33baa51b1196@gmail.com> (raw)
Hello,
It is quite clear that there are zero cares being given to making sure
that GDB scripts continue to work after making changes to core kernel
code, and why would you, because you probably did not know those
existed, but they do and they are used, and useful.
A recent example that was fixed by Kuan-Ying is this:
and now of course, "lx-interupts" also stopped working altogether after
this change:
https://lore.kernel.org/r/20230519134902.1495562-4-sdonthineni@nvidia.com
and who knows what else I could not test that is also broken.
We really need to find a better way to stop breaking GDB scripts, they
break way too often to be even remotely usable, and this is really sad.
It is also quite clear that we do not have enough continuous integration
and regression testing to ensure those breakages are caught ahead of time...
</rant>
--
Florian
next reply other threads:[~2023-11-29 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:48 Florian Fainelli [this message]
2023-11-29 23:06 ` No care given to GDB scripts Andrew Morton
2023-11-30 0:23 ` Florian Fainelli
2023-11-30 1:02 ` Andrew Morton
2023-11-30 4:49 ` Florian Fainelli
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=cfc3aa17-0f1b-4ffc-b848-33baa51b1196@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdonthineni@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox