WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Debugging Xen

To: "George Dunlap" <dunlapg@xxxxxxxxx>
Subject: Re: [Xen-devel] Debugging Xen
From: "David Pilger" <pilger.david@xxxxxxxxx>
Date: Tue, 2 Jan 2007 17:44:04 +0200
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Jan 2007 07:43:48 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fhE9UW/OdSvxiQVlqOnwJyzsWdXYzB1eL+YVdMlNV9+8T57D3L7vYa3UY0oiaacgW8ph7p5tPBU/NXIdml2klYRE7M655E+v5S5YLThgqebmEqGdj9biQcBKF9gLnoE9EsbNuqgb7p2RngBOwY/cJRJAc0R+dHFuRhtGpdGoJtU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <de76405a0701020728j2c9f7a52w121f571720ee2254@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <280848580612310819u77eb891au41017625fc010641@xxxxxxxxxxxxxx> <C1BDA810.68FC%Keir.Fraser@xxxxxxxxxxxx> <280848580701010107y7c5c3249t7a8d443ec69e41d2@xxxxxxxxxxxxxx> <200701020839.42037.Christoph.Egger@xxxxxxx> <280848580701020446h5dcafdddj3ca12ee6b194dee3@xxxxxxxxxxxxxx> <de76405a0701020728j2c9f7a52w121f571720ee2254@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 1/2/07, George Dunlap <dunlapg@xxxxxxxxx> wrote:
The vast majority if my dev experience has been in kernel and
hypervisor, so I'm not familiar with using a debugger, but the idea of
just changing the result of an "if" statement as it's running seems a
little strange to me. :-)  I think ideally you'd want to generate a
test input that would trigger the "other" if clause naturally.


Hi George,

In certain application this is right, we both agree that code coverage
is important in order to find bugs. The difference is that with a
debugger you check alternate code flow in run-time, and without it you
have to compile different version for each check.

Run time flow alternations could be made in other ways than a
debugger, but a debugger is more flexible and a lot of logic can be
built at the client side, this lets you automate QA processes, etc...

And ofcouse, a debugger has a zillion other uses as well :-)

Thanks,
David.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>