The two computers are from the same client, right? Have they installed anything
wired like Theeming software (other than Microsoft's theeming), screen readers,
anything that might interfere with normal Windows processing? Other then that
fixing Access Violation is difficult because the cause of the error is not
necessary where the error manifests itself. Example: in one place you free an
global object without making it nil and then you use the very same object from
somewhere else in your application. The error is going to pop at the second
place in the application, but the cause is at the first place in the
application.
Since I'm pretty sure you can't reproduce the error on your own computer you'll
need to modify the code in such a way that the MadExcept code would give you
more to work with. I'm suggesting compiling your application with a modified
version of the Controls.pas unit that puts more information into the Stack
Frame! You'd have to make whatever changes you feel are needed in Controls.pas
then put an nice button on a form that does "raise Exception.Create('Bang');"
and look at the exception log, to see if your changes really do provide extra
more information to track down the problem.
--
Cosmin Prund
> -----Mesaj original-----
> De la: [email protected] [mailto:[email protected]] În
> numele Ross Levis
> Trimis: Thursday, January 29, 2009 2:02 AM
> Către: 'Borland's Delphi Discussion List'
> Subiect: Re: Access violation in Delphi 7 unit - Help!
>
> 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:[email protected]]
> 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 -> [email protected]
> http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list -> [email protected]
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
