From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] .gdbinit: load QEMU sub-commands when gdb starts
Date: Wed, 17 May 2017 10:07:03 -0500 [thread overview]
Message-ID: <89400e9a-7f1e-7f86-a416-7365d943e703@redhat.com> (raw)
In-Reply-To: <20170517124042.1430-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
On 05/17/2017 07:40 AM, Stefan Hajnoczi wrote:
> The scripts/qemu-gdb.py file is not easily discoverable. Add a .gdbinit
> file so GDB either loads qemu-gdb.py automatically or prints a message
> informing the user how to enable them (some systems disable ./.gdbinit
> loading for security reasons).
>
> Symlink .gdbinit and the scripts directory in order to make out-of-tree
> builds work. The scripts directory is used to find the qemu-gdb.py file
> specified by a relative path in .gdbinit.
>
> Suggested-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v2:
> * Support out-of-tree builds [Daniel, Markus]
Tested-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-05-17 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 12:40 [Qemu-devel] [PATCH v2] .gdbinit: load QEMU sub-commands when gdb starts Stefan Hajnoczi
2017-05-17 13:55 ` Alex Bennée
2017-05-17 15:07 ` Eric Blake [this message]
2017-05-17 17:23 ` Philippe Mathieu-Daudé
2017-05-18 9:10 ` Stefan Hajnoczi
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=89400e9a-7f1e-7f86-a416-7365d943e703@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).