It will find all the little things, like memory leaks, that you don't
think cause stack overflows etc ;)
The key is to run it until you dont get a log file popping up anymore, and
then let us know if you still have a stack overflow problem...
Good luck.. Make sure Stack is turned on in compiler options etc, and td32
debug info to get relevant information.
On Wed, 30 Nov 2005 01:11:51 +1300, Ross Levis <[EMAIL PROTECTED]>
wrote:
I haven't used memcheck before but I've just downloaded it and will give
it a go tomorrow. I presume it can check for stack overflow problems.
----- Original Message -----
From: "Kyley Harris" <[EMAIL PROTECTED]>
To: "NZ Borland Developers Group - Delphi List" <[email protected]>
Sent: Tuesday, November 29, 2005 11:52 PM
Subject: Re: [DUG] app terminating abruptly
Do you use memcheck?
If you do not, then you might do yourself the kindness of running it and
seeing what comes up
as far as memory overruns, memory leaks etc. then submit the log file.
if you do use it, and its clean, then only examination of your code will
find your problem.
On Tue, 29 Nov 2005 23:42:01 +1300, Ross Levis
<[EMAIL PROTECTED]>
wrote:
The problem code I fixed turned out to not be the cause of the app
termination. It's still occuring, just less often for some reason.
While I'm running in the debugger, I occasionally get an access
violation at 0220F750. It is always the same location and I suspect
this must be causing the instant termination when not running in the
debugger.
In the CPU window if I click "Caller", it jumps to a function
called IsChild inside USER32.DLL. EAX = 7FFDD000
I'm not sure where to go from here to track this down to code in my
app!
I don't think it is a stack overflow problem since the program has
been
running for 2 days on another PC now, and I've had the problem occur
in
the debugger within only a few minutes.
It is not a thread issue. The error is occuring in the main thread
and
I've checked the other thread code and no unprotected access of the
main
thread is occuring.
The only one thought I had was with the fisSharedMemory component.
This
uses a file mapping system but without a file. I'm accessing the same
memory block written in one app and being read in another app at 50ms
intervals in both apps, with no locking protection or anything like
that. I'm not worried about reading incorrect data, but surely this
cannot cause an access violation to a memory location that seems
totally
unrelated, or could it?
Cheers,
Ross.
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
--
Kyley Harris
+64-21-671821
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
