From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avery Pennarun Subject: Re: still can't start domain Date: Thu, 8 Jul 2004 11:25:58 -0400 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <20040708152558.GD2502@worldvisions.ca> References: <20040708122210.GB27317@cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Mark Williamson Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org On Thu, Jul 08, 2004 at 04:15:09PM +0100, Mark Williamson wrote: > Hopefully we can add features to make debugging less of an issue as this new > code matures. Any suggestions that could improve debug-ability,etc are (as > always) encouraged. Clearer error messages than "Error: Cannot start domain" would probably be a good start. Anyone could have figured out in short order that the domain couldn't be started. What's much more important is *why* the domain couldn't be started. In general, error messages should always say why an operation failed, not just that the operation failed. I find that this works wonders in my own programs. In C programs, for example, always print out 'errno' in any error message where it could possibly be relevant. (Of course, to avoid confusion, definitely don't print out errno where it's not valid anymore :)) The errno equivalent in perl is $!. In python I guess you have to use exceptions or something. Have fun, Avery ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com