From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Re: Error reporting capabilities for libxc Date: Tue, 24 Oct 2006 09:47:08 +0200 Message-ID: <453DC4FC.7040902@suse.de> References: <453D1554.8000202@us.ibm.com> <20061023192753.GG25795@redhat.com> <3AAA99889D105740BE010EB6D5A5A3B205073B@paddington.ad.cl.cam.ac.uk> <20061023205730.GI25795@redhat.com> <3AAA99889D105740BE010EB6D5A5A3B205073C@paddington.ad.cl.cam.ac.uk> <453D30D3.6090007@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <453D30D3.6090007@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: Ian Pratt , xen-devel@lists.xensource.com, "Daniel P. Berrange" List-Id: xen-devel@lists.xenproject.org Anthony Liguori wrote: > I know it's a bigger patch, but the Right Thing to do here is to just > propagate an error code through the libxc functions. That doesn't allow a descriptive text message, which is often quite useful to figure what went wrong in detail. error codes such as errno == EINVAL are not very helpful for trouble shooting ... What number space we are talking about btw? errno? something else? cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg