[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] monitor: Add port write command

From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH] monitor: Add port write command
Date: Wed, 15 Jul 2009 07:36:48 -0500
User-agent: Thunderbird (X11/20090320)

Paul Brook wrote:
If you don't have qemu sources than I really don't care. By definition you're not going to be able to do anything useful even if you do figure out what the problem is. Note that there's no requirement that you run gdb on the target itself. Remote debug (e.g. via gdbserver on linux) is a well established technique.

Likewise for debugging stripped production binaries, my answer is "don't do that". There are very rare cases where a bug goes away on a debug build, but in those cases any instrumentation you add is also liable to make the bug go away.

If we had an info device, it would fall into the same category as info cpu or info registers. It duplicates the functionality of the gdbstub but it provides a convenience interface for those who don't have gdb connected.

Since there isn't really an obvious way to expose the device state via gdb without using Rcmd and a new monitor command, the whole debate seems academic :-)


Anthony Liguori

reply via email to

[Prev in Thread] Current Thread [Next in Thread]