From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DiI17-0001pP-B2 for qemu-devel@nongnu.org; Tue, 14 Jun 2005 16:28:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DiI13-0001o3-I2 for qemu-devel@nongnu.org; Tue, 14 Jun 2005 16:28:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DiI13-0001nn-FT for qemu-devel@nongnu.org; Tue, 14 Jun 2005 16:28:09 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DiI1c-00058f-30 for qemu-devel@nongnu.org; Tue, 14 Jun 2005 16:28:44 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j5EKRIRu026818 for ; Tue, 14 Jun 2005 16:27:19 -0400 (EDT) Date: Tue, 14 Jun 2005 16:27:12 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Norton Ghost crashes with page fault for me too. Message-ID: <20050614202712.GA32761@jbrown.mylinuxbox.org> References: <002c01c57104$877421b0$334d21d1@organiza3bfb0e> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002c01c57104$877421b0$334d21d1@organiza3bfb0e> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, Jun 14, 2005 at 12:14:05PM -0500, jeebs@yango.us wrote: > Not all of us are developers. > > The best that many can do is test qemu and report problems when they are > found. > > Some of us do a bit more, by deliberately testing qemu with lots of > software, looking for bugs. And reporting bugs when they are found. If you really want a bug to be fixed badly, and you have no idea of how to fix it, what you need to do is contact the developer of that code and let that person know about the bug. E.g. I'm the developer of the gtk2 interface for qemu, and I have no idea about what bugs it may have as no one has reported any to me. In fact, I have no idea if anyone is even using it because I get no direct feedback. This is especially true for using the gtk2 interface under Windows, because I am unable to test the code there. If someone who could test it did, and told me about the bug, I'd fix it right away. The only problem with this approach is that the section of code you are interested in having fixed may not have an active developer (person left a while ago or it was a section written by Fabrice himself that he doesn't have time to go over anymore). In that case, there isn't much you can do. Documenting bugs is still good because a) we can let other users know its a known bug and b) when a new maintainer for that section of code comes along, they'll be able to get started on the fixes right away. But this is only satisfactory if you are a very patient person. > > But that's no excuse for bug reports to just vanish into the void. Without > an awknowledgement or somebody writting it down as a bug in qemu that needs > to get fixed eventually. > No one looks at the Savanah bug tracker because its never been used. If you were to say submit every unfixed bug you found there, just maybe those of us who bother to look every once in a while will see it and fix it. Do this often enough and others will use it, etc... the qemu user forum and the qemu irc channel developed in much the same way. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.