From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fernando Nasser To: Steven Johnson Cc: insight@sources.redhat.com Subject: Re: 2 Segfaults in Insights (Latest CVS) Date: Thu, 12 Oct 2000 08:34:00 -0000 Message-id: <39E5D9FB.8FAAB269@cygnus.com> References: <39E418FB.46E1EA66@ozemail.com.au> X-SW-Source: 2000-q4/msg00073.html Steven Johnson wrote: > > I think it could be forced on any Insight by creating a hook on load that > updates a register to some arbitrary value. For example: > > define hook-load > set $eax=0x01 > set $eax=0x00 > end > You know why? Because the "after idle" event that is causing the damage was created when the first set command was completed. As the GUI did not become idle the event was still there and it happened to occur in the middle of the second register write operation (from the second set). Again, very nice detective work. I thought tracking this down would be difficult but with all the info you tracked down it will be a piece of cake :-) -- Fernando Nasser Red Hat Canada Ltd. E-Mail: fnasser@cygnus.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9