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

[Gleb Natapov]

On Wed, Jul 15, 2009 at 11:14:20AM +0100, Paul Brook wrote:
> > > I'd be reluctant to expose the savevm state to the user.
> > >
> > > For debugging qemu I don't see it providing any real benefit over firing
> > > up GDB and poking directly at the device directly.
> >
> > Not all environments where you need to debug things have gdb, qemu
> > sources or even non striped qemu binary.
> 
> If you don't have qemu sources than I really don't care. By definition you're 
I noticed that you don't care, but I do.

> 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 
I will be able to fix the bug if I'll figuring out what the problem is,
so I don't see how this is not useful.

> itself. Remote debug (e.g. via gdbserver on linux) is a well established 
> technique.
> 
Client will not allow me near his infrastructure, he is nice enough to
dump device state for me if it's simple.

> 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.
> 
Have you sees a real production environment and tried to resolve real
customer bugs? Just asking.

--
                        Gleb.