On Mon, Oct 15, 2007 at 01:10:45PM +0100, Richard W.M. Jones wrote:
Did this problem get fixed while I was away?
What I'm seeing in Veerendra's valgrind log are the following suspicious
messages, although the line numbers don't correspond to the earlier line
numbers from gdb:
yeah, I
Veerendra wrote:
Now when I am running virsh using the valgrind it is listing fine!!
But when I am trying to run virsh alone it is dumping the core again.
Attaching the valgrind.log file also.
Does anyone knows why this is behaving as above ?
And the virsh start for my domu1, which is
On Wed, Oct 10, 2007 at 04:44:36PM +0530, Veerendra wrote:
Veerendra wrote:
Now when I am running virsh using the valgrind it is listing fine!!
But when I am trying to run virsh alone it is dumping the core again.
Attaching the valgrind.log file also.
Does anyone knows why this is
Daniel Veillard wrote:
I still don't understand how you could get there (remote code
while using xen:///) and why this could crash, except for a previous
memory corruption.
Please run the same command under valgrind and report,
thanks,
Daniel
Now when I am running virsh using the valgrind
