On 03/24/2010 09:38 AM, Andi Kleen wrote:
If you're profiling a single guest it makes more sense to do this from
inside the guest - you can profile userspace as well as the kernel.
I'm interested in debugging the guest without guest cooperation.
In many cases qemu's new gdb stub works for that, but in some cases
I would prefer instruction/branch traces over standard gdb style
debugging.
Isn't gdb supposed to be able to use branch traces? It makes sense to
expose them via the gdb stub then. Not to say an external tool doesn't
make sense.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
