I would be delighted to do this.
Please yes!

But it is turning out to be difficult. Not sure why.

What I have is a suite of applications, using about 150 BPLs (Delphi
5). So it takes a bit of effort to change the options for all the
packages. I believe I now have all the debugging options set correctly.

Yet now the application simply crashes on the first line. According to
the CPU window, it is in a format string routine (presumably trying to
build an error string for display while handling an exception?)

The line it tripped over is not worth mentioning, it is simple and has
been there forever. What I am thinking is that I have somehow not
included/used MemCheck correctly for my situation (packaged app).

I put the source in my lowest level base package and called MemCheck
at startup. Is this not all that is required?

Any advice?

Meantime, I can try building simple applications or standalone
executables to generate a log and will cheerfully submit that instead.

When I do this, I am still scratching my head over how to map the
results to anything meaningful in my code.

I am also using the JEDI libraries, and have my own exception handler.
Do these interfere with MemCheck in any known way? I saw a conditional
define for {$DEFINE USE_JEDI_JCL} and tried that also.

I only get a log for the simplest case (Unit1/Project1 test case as
shown at
http://v.mahon.free.fr/pro/freeware/memcheck/tutorial_findleaks.htm

Otherwise MemCheck either (1) crashes immediately (my current
situation), or (2) reports a "second release of block attempt" (sounds
promising! but then... no log file, no stopping any where meaningful,
no call stack, no way to understand where I am.

So I'm having trouble getting this log file. Will revert to a
standalone simplified test app and try again.

Meantime any hints greatly appreciated. Thank you in advance.





--- In [email protected], Walter Prins <[EMAIL PROTECTED]> wrote:
>
> Can you post the MemCheck log when it bombs please? (Make sure 
> everything is built with TD32 debug info on, and as much debugging info 
> included as possible, so the memcheck log is more useful than it would 
> otherwise be please.)
> 
> Walter
> 
> Steward wrote:
> >
> >
> > I have tried EurekaLog, MemProof and MemCheck (tools available via
> > google), but ended up drowning in a flood of information which is
> > either irrelevant or meaningless to me.
> >
> >   
> 
> 
> [Non-text portions of this message have been removed]
>


Reply via email to