From mint-bounce@lists.fishpool.fi Sun Dec 20 14:33:33 2009 Message-ID: <4B2E7B67.3030908@freesbee.fr> Date: Sun, 20 Dec 2009 20:30:47 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Potential bug on mouse wheel References: <4B2E6BAE.8070300@online.no> <00183c90.019ad6d60603@smtp.freeola.net> <4B2E756A.7030100@online.no> In-Reply-To: <4B2E756A.7030100@online.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 091220-0, 20/12/2009), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nBKJXRxw004003 Jo Even Skarstein wrote: > As this "bug" has only been observed in Thing I'd say that Thing was > already broken. It just worked by coincidence. The fact that it doesn't > happen in 1.29 indicates that there indeed was a bug in Thing, and that > it has been fixed. So I don't think it's necessary to spend more time on > this. Maybe, or maybe not. Thing 1.27 could be the victim of some random memory overwrite (such as the ones that can occur if there are register problems in the GemLib). This is very serious. Running FreeMiNT with memory protection enabled could provide additional information. However I don't know if illegal memory accesses can be detected from kernel modules. -- Vincent Rivière