From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K0nCy-0005bq-U6
	for qemu-devel@nongnu.org; Mon, 26 May 2008 20:38:32 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K0nCw-0005Y4-GE
	for qemu-devel@nongnu.org; Mon, 26 May 2008 20:38:31 -0400
Received: from [199.232.76.173] (port=59988 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K0nCw-0005Xv-DZ
	for qemu-devel@nongnu.org; Mon, 26 May 2008 20:38:30 -0400
Received: from mail.codesourcery.com ([65.74.133.4]:44494)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1K0nCv-0004v2-Te
	for qemu-devel@nongnu.org; Mon, 26 May 2008 20:38:30 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Status of sun4u emulation?
Date: Tue, 27 May 2008 01:38:25 +0100
References: <20080526154349.GA19767@vimes.madsworld.lan>
	<20080526194445.GA5479@vimes.madsworld.lan>
	<f43fc5580805261256u1d9a1129if622d14709050cc1@mail.gmail.com>
In-Reply-To: <f43fc5580805261256u1d9a1129if622d14709050cc1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200805270138.25803.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>

> > =C2=A0/home/mad/src/svn/qemu/tcg/tcg.c:1700: tcg fatal error
> > =C2=A0qemu: uncaught target signal 6 (Aborted) - exiting

> These error messages could be more descriptive, like what is the
> problem and how to fix it.

=46WIW The general theory with aborts is that that should never occur so th=
ere's=20
no point being verbose.

=46rom a user perspective "tcg.g:1700 fatal error" is IMHO no worse than "B=
ad=20
voodoo when trying to frobnicate the weezle". The user has no control over=
=20
weasel frobnication, so it just adds confusion.

=46or someone fixing the bug you're likely to need additional instrumentati=
on, a=20
debugger and/or a core dump anyway so the file and line number is sufficien=
t=20
context.

Of course there are exceptions to this rule, but if it were easy to report =
the=20
problem and how to fix it we'd have done so already :-)

Paul