| Re: [AD] Mouse problems in Windows affected by this revision? |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Mouse problems in Windows affected by this revision?
- From: "Trent Gamblin" <trent@xxxxxxxxxx>
- Date: Thu, 12 Mar 2009 11:27:26 -0600 (MDT)
On Thu, March 12, 2009 11:14 am, Elias Pschernig said:
> On Thu, 2009-03-12 at 10:49 -0600, Trent Gamblin wrote:
>> On Thu, March 12, 2009 10:42 am, Evert Glebbeek said:
>> > On 12 Mar 2009, at 9:35 , Trent Gamblin wrote:
>> >> This looks innocent enough but revision 11640 works and 11641 does
>> >> not. Anyone have any idea why this might cause
>> >> problems? I already added 100 "unknown" key names in the key name
>> >> array, that didn't fix it.
>> >
>> > Have you tried running through valgrind to look for out-of-bound array
>> > access? That's all I can think of right now.
>>
>> Unfortunately there is no valgrind for Windows and no free tool like
>> it that I know of. I could run it on Linux, that still might help
>> though.
>>
>
> What does "works" mean? Are some keys not reported any longer?
It's a completely unrelated error that I reported before. I get
assertions from the mouse code which show all the signs of
memory corruption somewhere, but I don't know where.
Trent :{)>