 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Ignacio Vazquez
Guest
|
 Posted: Thu Aug 07, 2003 1:44 pm Post subject: Re: Finding what caused AV |
 |
|
"Mark Payton" <mark.payton (AT) derbyshire (DOT) gov.uk> wrote in message
3f324171$1 (AT) newsgroups (DOT) borland.com...
| Quote: | Is there anyway I can found out what called the ClientToScreen and trace
it back through to my component.
|
Use a tool like madExcept.
http://www.madshi.net/
Cheers,
Ignacio
--
No, don't send me e-mail directly. No, just don't.
|
|
| Back to top |
|
 |
Ignacio Vazquez
Guest
|
| Posted: Thu Aug 07, 2003 4:34 pm Post subject: Re: Finding what caused AV |
|
|
"Mark Payton" <mark.payton (AT) derbyshire (DOT) gov.uk> wrote in message
3f327e29$1 (AT) newsgroups (DOT) borland.com...
| Quote: | Thanks, would this work in the runtime environment, the error doesnt
happen in the IDE
|
Yes.
Cheers,
Ignacio
--
No, don't send me e-mail directly. No, just don't.
|
|
| Back to top |
|
|
Mark Payton
Guest
|
| Posted: Thu Aug 07, 2003 4:37 pm Post subject: Re: Finding what caused AV |
|
|
Thanks, would this work in the runtime environment, the error doesnt happen
in the IDE
Mark
"Ignacio Vazquez" <ivazquezATorioncommunications.com> wrote
| Quote: | "Mark Payton" <mark.payton (AT) derbyshire (DOT) gov.uk> wrote in message
3f324171$1 (AT) newsgroups (DOT) borland.com...
Is there anyway I can found out what called the ClientToScreen and trace
it back through to my component.
Use a tool like madExcept.
http://www.madshi.net/
Cheers,
Ignacio
--
No, don't send me e-mail directly. No, just don't.
|
|
|
| Back to top |
|
|
Richard Atkinson
Guest
|
| Posted: Fri Aug 08, 2003 12:10 am Post subject: Re: Finding what caused AV |
|
|
I hadn't seen madExcept. It looks very useful.
Another option is the Post Mortem Review that is part of Helmuth Adolph's
wonderful ProDelphi.
ProDelphi might not be as flashy as some other profilers but I have been
very impressed with Helmuth's fast and helpful response to support requests
and I trust his program.
FWIW
Richard Atkinson
|
|
| Back to top |
|
|
Eugene Mayevski
Guest
|
| Posted: Fri Aug 08, 2003 5:14 pm Post subject: Re: Finding what caused AV |
|
|
Mark Payton wrote:
| Quote: | I get and intermittent AV in Controls.pas ClientToScreen
Is there anyway I can found out what called the ClientToScreen and trace it
back through to my component.
|
Obviously, you are calling (directly or via VCL) the method of the
control that has been destroyed already.
First thing to do is to replace all calls to free with FreeAndNil. What
this does -- whenever the disposed object is used, you will get an AV at
address 0. Then you will know that the cause of the problem is access
to freed object. Why this is necessary -- if you don't set object
references to nil after destroying them, some of the calls to this
object will succeed (because the memory is still valid), but later you
will get an AV and that AV will tell you nothing meaningful.
--
Eugene Mayevski
Flexible cross-platform information exchange framework
http://www.msgconnect.com/
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
