Those types of problems are hair-pullers, in fact I had a user a couple of weeks ago who was getting C000001D external exceptions when he printed a report, and no one else is getting them. Then the C000001D went away by itself! Have to love this stuff...
Anyway, I'd look at the following: 1) Make sure the user is running antivirus and firewall software 2) See if there was a recent addition of some software (a driver for some new hardware?) that has a background process that monitors mouse movements; that might be causing an interaction 3) Have the user run diagnostics on his system. Although for these symptoms it doesn't sound likely (especially since there are 2 PCs having them), I've found that cross-linked files or failing hard drives can cause all sorts of problems that appear to be in the program code 4) When I don't have access to a system to debug a problem, I create a build that has MessageDlg statements peppered through it telling me where the program is (e.g. message might be "Checkpoint 8719" where 8719 is the line number in the source code), then I ask the user to run it and give me the last checkpoint before the blowup. In this case, it sounds like the problem might be in an onActivate or onEnter event, so I'd put MessageDlg statements into those and see if it tells me something. (E.g. put "Checkpoint: Entering onActivate" and "Checkpoint: Exiting onActivate" messages in, then if you get the first but not the second, you have it narrowed down. Then another build to narrow it down further. I find that if a user has to click through hundreds of "Checkpoint" messages, they will get tired and stop, so I like to do it in 3 or 4 builds to narrow down the problem area with as few messages as possible.) At 05:02 PM 1/28/2009, Ross Levis wrote: >I was wrong about it always occurring while minimizing. Here is another >report, this one from the other PC. It apparently just occurred moving the >mouse over the window, and appears related to displaying a hint, but the >crash is in the exact same location as the minimize. > > > >exception message : Access violation at address 004BBE48 in module >'MyProgram.exe'. Read of address 3D579DE8. > > > >Main ($764): > >004bbe48 MyProgram.exe Controls 4645 +53 TControl.WndProc > >004beea7 MyProgram.exe Controls 6342 +33 TWinControl.WndProc > >004d55d5 MyProgram.exe Forms 3102 +103 TCustomForm.WndProc > >004beb24 MyProgram.exe Controls 6237 +3 TWinControl.MainWndProc > >00475fa4 MyProgram.exe Classes 10966 +8 StdWndProc > >7c90eae0 ntdll.dll KiUserCallbackDispatcher > >004c2bb3 MyProgram.exe Controls 8719 +1 THintWindow.ActivateHintData > >004dcf8a MyProgram.exe Forms 7594 +57 TApplication.ActivateHint > >004dc917 MyProgram.exe Forms 7386 +20 TApplication.HintMouseMessage > >004bbd9d MyProgram.exe Controls 4612 +20 TControl.WndProc > >004beea7 MyProgram.exe Controls 6342 +33 TWinControl.WndProc > >004d55d5 MyProgram.exe Forms 3102 +103 TCustomForm.WndProc > >004bbc18 MyProgram.exe Controls 4552 +5 TControl.Perform > >004bec08 MyProgram.exe Controls 6258 +4 GetControlAtPos > >004beca0 MyProgram.exe Controls 6277 +10 TWinControl.ControlAtPos > >004bbc18 MyProgram.exe Controls 4552 +5 TControl.Perform > >004bed3e MyProgram.exe Controls 6301 +15 TWinControl.IsControlMouseMsg > > > >I would have been thinking it was a Windows or computer issue of some sort, >but when it occurs on 2 independent computers, I'm not sure I can get away >with that explanation. > > > >Thanks, > >Ross. > > > >From: Ross Levis [mailto:r...@stationplaylist.com] >Sent: Thursday, 29 January 2009 12:50 p.m. >To: 'Borland's Delphi Discussion List' >Subject: Access violation in Delphi 7 unit - Help! > > > >A user running my software on 2 separate computers for several months has >reported that an access violation has suddenly started occurring on both >computers when simply minimizing the application. > > > >I gave him a build with MadExcept compiled in, and he sent this crash >report. > > > >exception message : Access violation at address 004BBE48 in module >'MyProgram.exe'. Read of address 3D579DE8. > > > >Main ($7a8): > >004bbe48 MyProgram.exe Controls 4645 +53 TControl.WndProc > >004beea7 MyProgram.exe Controls 6342 +33 TWinControl.WndProc > >004d55d5 MyProgram.exe Forms 3102 +103 TCustomForm.WndProc > >004beb24 MyProgram.exe Controls 6237 +3 TWinControl.MainWndProc > >00475fa4 MyProgram.exe Classes 10966 +8 StdWndProc > >7c90eae0 ntdll.dll KiUserCallbackDispatcher > >77d5538a USER32.dll SetActiveWindow > >004db5b4 MyProgram.exe Forms 6695 +4 TApplication.Minimize > >004db05f MyProgram.exe Forms 6541 +10 TApplication.WndProc > >004d7786 MyProgram.exe Forms 4214 +4 TCustomForm.WMSysCommand > >004bbe48 MyProgram.exe Controls 4645 +53 TControl.WndProc > >004beea7 MyProgram.exe Controls 6342 +33 TWinControl.WndProc > >004d55d5 MyProgram.exe Forms 3102 +103 TCustomForm.WndProc > >004beb24 MyProgram.exe Controls 6237 +3 TWinControl.MainWndProc > >00475fa4 MyProgram.exe Classes 10966 +8 StdWndProc > >77d4b7a6 USER32.dll SendMessageW > >77d4e025 USER32.dll DefWindowProcA > >77d4e361 USER32.dll CallWindowProcA > >004bef8b MyProgram.exe Controls 6369 +23 TWinControl.DefaultHandler > >004d6a52 MyProgram.exe Forms 3774 +7 TCustomForm.DefaultHandler > >004bc125 MyProgram.exe Controls 4743 +2 TControl.WMNCLButtonDown > >004d74e5 MyProgram.exe Forms 4102 +12 TCustomForm.WMNCLButtonDown > > > >What on Earth could be the problem? Hundreds of other users are using the >software with no problems. > > > >Any thoughts very welcome! > > > >Thanks, > >Ross. > >_______________________________________________ >Delphi mailing list -> Delphi@elists.org >http://lists.elists.org/cgi-bin/mailman/listinfo/delphi Regards, Sid Gudes PIA Systems Corporation sid.gu...@piasystems.com _______________________________________________ Delphi mailing list -> Delphi@elists.org http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
