public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Little Tree <littletreetrunk32@gmail.com>
To: gdb@sourceware.org
Subject: Linux kernel debugging - make scripts_gdb - Error
Date: Wed, 12 Apr 2023 15:58:59 +0530	[thread overview]
Message-ID: <CAHwOCLZAP2_scz5NXF7F=PD+g4Of53H51vTnWbxCg6+G4899Fg@mail.gmail.com> (raw)

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

I am remotely debugging an AArch64 Linux kernel running on QEMU using gdb.
I wish to make use of the Python support while debugging (for using the
commands like lx-dmesg).
Referring to this link
https://docs.kernel.org/dev-tools/gdb-kernel-debugging.html , I understand
that for Linux kernel 5.1 and above, the scripting support is to be built
using the command "make scripts_gdb" after the Linux kernel is built. I am
getting many errors while building (mostly related to x86).

Do I have to set any arm specific environment variable before building? At
present my build command is

$make scripts_gdb


Thanks a lot,
  Little

             reply	other threads:[~2023-04-12 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 10:28 Little Tree [this message]
2023-04-12 17:51 ` Luis Machado

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='CAHwOCLZAP2_scz5NXF7F=PD+g4Of53H51vTnWbxCg6+G4899Fg@mail.gmail.com' \
    --to=littletreetrunk32@gmail.com \
    --cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).