From: Janosch Frank <frankja@linux.vnet.ibm.com>
To: Andrew Jones <drjones@redhat.com>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH] dump-guest-memory: more descriptive lookup_type failure
Date: Wed, 14 Mar 2018 16:12:21 +0100 [thread overview]
Message-ID: <203683e2-773b-d23c-423b-598ea98a98d5@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180314142133.14166-1-drjones@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On 14.03.2018 15:21, Andrew Jones wrote:
> We've seen a few reports of
>
> (gdb) source /usr/share/qemu-kvm/dump-guest-memory.py
> Traceback (most recent call last):
> File "/usr/share/qemu-kvm/dump-guest-memory.py", line 19, in <module>
> UINTPTR_T = gdb.lookup_type("uintptr_t")
> gdb.error: No type named uintptr_t.
Oh yeah, I remember that particular error.
Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
>
> This occurs when symbols haven't been loaded first, i.e. neither a
> QEMU binary was loaded nor a QEMU process was attached first. Let's
> better inform the user of how to fix the issue themselves in order
> to avoid more reports.
>
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> scripts/dump-guest-memory.py | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/dump-guest-memory.py b/scripts/dump-guest-memory.py
> index 51acfcd0c053..e56fff6d7e82 100644
> --- a/scripts/dump-guest-memory.py
> +++ b/scripts/dump-guest-memory.py
> @@ -16,7 +16,11 @@ the COPYING file in the top-level directory.
> import ctypes
> import struct
>
> -UINTPTR_T = gdb.lookup_type("uintptr_t")
> +try:
> + UINTPTR_T = gdb.lookup_type("uintptr_t")
> +except Exception as inst:
> + raise gdb.GdbError("Symbols must be loaded prior to sourcing dump-guest-memory.\n"
> + "Symbols may be loaded by first 'attach'ing a QEMU process id or by 'load'ing a QEMU binary.")>
> TARGET_PAGE_SIZE = 0x1000
> TARGET_PAGE_MASK = 0xFFFFFFFFFFFFF000
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2018-03-14 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:21 [Qemu-devel] [PATCH] dump-guest-memory: more descriptive lookup_type failure Andrew Jones
2018-03-14 14:24 ` no-reply
2018-03-15 19:26 ` Laszlo Ersek
2018-03-14 15:12 ` Janosch Frank [this message]
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=203683e2-773b-d23c-423b-598ea98a98d5@linux.vnet.ibm.com \
--to=frankja@linux.vnet.ibm.com \
--cc=drjones@redhat.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).