First off get memcheck - it's free. It does spot most issues quite quickly -
but will only spot issues directly related to memory allocations by Delphi's
memory manager.

        http://v.mahon.free.fr/pro/freeware/memcheck

If that fails, for real serious stuff go buy BoundsChecker from NuMega.

Myles.


-----Original Message-----
From: Rohit Gupta [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 25 February 2004 18:22
To: Trevor Jones; NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Critical Sections


Back to square 1.  :-(

We are having severe problems with our apps either freezing and 
crashing a rather too regularly.  It appears to be memory trashing.  
We can replicate in a rather simplish app so we dont think we have 
stuffed up...  But everything and everybody's code is suspect.... 
thats IBO, Borland and Windows.

The frequency of error is proportional to number of threads, number 
of memory allocations.  Often it is so severe that the exception has 
an exception and the stack is definitely trashed at this point.


From:                   "Trevor Jones" <[EMAIL PROTECTED]>
To:                     "NZ Borland Developers Group - Delphi List"
<[EMAIL PROTECTED]>
Subject:                Re: [DUG] Critical Sections
Date sent:              Wed, 25 Feb 2004 16:10:38 +1300
Send reply to:          Trevor Jones <[EMAIL PROTECTED]>,
        NZ Borland Developers Group -
        Delphi List <[EMAIL PROTECTED]>
        <mailto:[EMAIL PROTECTED]>
        <mailto:[EMAIL PROTECTED]>

> Rohit,
>   no, not true at all....
> 
>   When you receive WM_TIMER messages, they come in through the app's
message
> loop which is running in the main VCL thread.
> 
>   You can run into the problems to (which I believe) you allude if you you
> use SetTimer with a null window handle and use a callback proc instead,
but
> very few programs use this kind of timer.
> 
> HTH
> Trevor
> 
> ----- Original Message ----- 
> From: "Rohit Gupta" <[EMAIL PROTECTED]>
> To: "NZ Borland Developers Group - Delphi List" <[EMAIL PROTECTED]>
> Sent: Wednesday, February 25, 2004 4:46 PM
> Subject: [DUG] Critical Sections
> 
> 
> > When a windows timer (created with SetTimer) is used with a non-
> > visible window (created with AllocateHWnd).  It receives
> > WM_TIMER messages...  Is it safe for this method/event to access
> > the VCL ?
> >
> > It appears to me that this should be using entercriticalsection for the
> > RTL.  Is this true ?
> > Regards
> >
> > Rohit
> >
> > ====================================================
> > ==================
> > CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New
> > Zealand
> > PH    (649) 489-2280
> > FX    (649) 489-2290
> > email [EMAIL PROTECTED]  or  [EMAIL PROTECTED]
> > ====================================================
> > ==================
> >
> >
> > _______________________________________________
> > Delphi mailing list
> > [EMAIL PROTECTED]
> > http://ns3.123.co.nz/mailman/listinfo/delphi
> >
> >
> 
> 
> _______________________________________________
> Delphi mailing list
> [EMAIL PROTECTED]
> http://ns3.123.co.nz/mailman/listinfo/delphi
> 

Regards

Rohit

======================================================================
CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New Zealand
PH    (649) 489-2280 
FX    (649) 489-2290
email [EMAIL PROTECTED]  or  [EMAIL PROTECTED]
======================================================================


_______________________________________________
Delphi mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/delphi

Reply via email to