From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56907) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RyQmy-0007BV-UE for qemu-devel@nongnu.org; Fri, 17 Feb 2012 11:36:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RyQmt-0000HI-3c for qemu-devel@nongnu.org; Fri, 17 Feb 2012 11:36:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:24258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RyQms-0000Go-Se for qemu-devel@nongnu.org; Fri, 17 Feb 2012 11:35:59 -0500 Message-ID: <4F3E81E9.8070505@redhat.com> Date: Fri, 17 Feb 2012 17:35:53 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1329211193-393-1-git-send-email-pbonzini@redhat.com> <1329211193-393-3-git-send-email-pbonzini@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] qdev: print error message before aborting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel On 02/17/2012 05:30 PM, Peter Maydell wrote: > So now you get: > qemu-system-arm: Insufficient permission to perform this operation > Aborted > > This still isn't really very diagnostic: I had to run the whole > thing under a debugger and look at the backtrace anyway before > I realised I'd hit the same problem again. Sorry. :) > Isn't there some way > to supply a more specific message than this? (some string that > actuall mentions at least one of "object", "property" and > "after initialization", for example :-)) Yes, of course. This should have been done from the beginning. I just cut-and-pasted the error message but that doesn't mean it is a good one. Paolo