Alexander Graf ag...@suse.de writes:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger than
Alexander Graf ag...@suse.de writes:
On 30.10.2011, at 15:30, Stefan Weil wrote:
Am 30.10.2011 14:41, schrieb Alexander Graf:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was
Am 31.10.2011 07:38, schrieb Markus Armbruster:
Alexander Graf ag...@suse.de writes:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when
On 10/30/2011 07:07 AM, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger than
1 MiB. QEMU normally uses 2 MiB on Linux
On Sun, Oct 30, 2011 at 01:07:26PM +0100, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger than
1 MiB. QEMU normally
Stefan Weil s...@weilnetz.de writes:
Am 31.10.2011 07:38, schrieb Markus Armbruster:
Alexander Graf ag...@suse.de writes:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not
Am 31.10.2011 19:22, schrieb Daniel P. Berrange:
On Sun, Oct 30, 2011 at 01:07:26PM +0100, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with
Am 31.10.2011 19:30, schrieb Markus Armbruster:
Copies are evil because we need to pick the one version that's right for
all our users. Repeatedly.
That's okay (sort of) when there's a tight coupling, and there's really
only one admissible version.
Or it may be a lesser evil when the thing
Am 31.10.2011 19:13, schrieb Anthony Liguori:
On 10/30/2011 07:07 AM, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger
On 10/31/2011 02:03 PM, Stefan Weil wrote:
Am 31.10.2011 19:13, schrieb Anthony Liguori:
On 10/30/2011 07:07 AM, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger than
1 MiB. QEMU normally uses 2 MiB on
Am 30.10.2011 14:41, schrieb Alexander Graf:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts when memalign is called with an alignment larger
On 30.10.2011, at 15:30, Stefan Weil wrote:
Am 30.10.2011 14:41, schrieb Alexander Graf:
On 30.10.2011, at 13:07, Stefan Weil wrote:
Valgrind is a tool which can automatically detect many kinds of bugs.
Running QEMU on Valgrind with x86_64 hosts was not possible because
Valgrind aborts
13 matches
Mail list logo
