From: Glenn Washburn <development@efficientek.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: Glenn Washburn <development@efficientek.com>,
linux-um <linux-um@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
Johannes Berg <johannes@sipsolutions.net>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Subject: [PATCH 0/2] GDB: Support getting current task struct in UML
Date: Tue, 14 Feb 2023 17:35:38 -0600 [thread overview]
Message-ID: <cover.1676416728.git.development@efficientek.com> (raw)
Hi all,
I noticed that running "call $lx_current()" with the kernel GDB helper
scripts was crashing when running in UML. So, I've fixed this. I'm not
100% sure this is correct or covers all corner cases, but I've done some
minimal testing. Perhaps someone on the linux-um list can review/comment
on whether this looks good or not.
There's also a trivial indentation fix in the same area.
Glenn
Glenn Washburn (2):
scripts/gdb: Correct indentation in get_current_task
scripts/gdb: Support getting current task struct in UML
scripts/gdb/linux/cpus.py | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
--
2.30.2
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next reply other threads:[~2023-02-14 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 23:35 Glenn Washburn [this message]
2023-02-14 23:35 ` [PATCH 1/2] scripts/gdb: Correct indentation in get_current_task Glenn Washburn
2023-02-15 7:44 ` Jan Kiszka
2023-02-14 23:35 ` [PATCH 2/2] scripts/gdb: Support getting current task struct in UML Glenn Washburn
2023-02-15 7:45 ` Jan Kiszka
2023-02-15 15:55 ` Glenn Washburn
2023-02-15 16:04 ` Jan Kiszka
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=cover.1676416728.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=jan.kiszka@siemens.com \
--cc=johannes@sipsolutions.net \
--cc=kbingham@kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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