Stefan Hajnoczi writes:
> On Mon, May 15, 2017 at 03:17:28PM +0100, Alex Bennée wrote:
>>
>> Stefan Hajnoczi writes:
>>
>> > 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 u
On Tue, May 16, 2017 at 11:45:56AM +0100, Stefan Hajnoczi wrote:
> On Mon, May 15, 2017 at 03:17:28PM +0100, Alex Bennée wrote:
>
> > How would it work for out-of-tree builds?
>
> ./.gdbinit assumes your current working directory is the root of the
> QEMU source tree. If gdb is launched outside
On Mon, May 15, 2017 at 03:17:28PM +0100, Alex Bennée wrote:
>
> Stefan Hajnoczi writes:
>
> > 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 syste
Stefan Hajnoczi writes:
> 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).
>
> Suggested-by:
On 05/15/2017 10:47 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).
Sug
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).
Suggested-by: Eric Blake
Signed-off-by: Stefan Hajn
