Seems my parallel program has memory corruption problem. The problem is
that it's a batch job, and the current environment does not allow to
debug it interactively. So I can only analyze the core file using dbx,
but it seems the memory was corrupted elsewhere, so the call stack of
the core file does not help.

Any idea?

Thanks!

On Wed, 7 Sep 2005, Patricia wrote:

> Seems my parallel program has memory corruption problem. The problem is
> that it's a batch job, and the current environment does not allow to
> debug it interactively. So I can only analyze the core file using dbx,
> but it seems the memory was corrupted elsewhere, so the call stack of
> the core file does not help.

Check out libumem and/or the watchmalloc library (see my book, Solaris
Systems Programming, for more info, and their respective man pages).

-- 
Rich Teer, SCNA, SCSA, OpenSolaris CAB member

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich

Use Purify from IBM (used to be Rational Software but IBM bought them).
It is now under the Rational brand at IBM.

This is what is does..

http://bmrc.berkeley.edu/purify/docs/html/installing_and_gettingstarted/2-purify.html

Patricia wrote:
> Seems my parallel program has memory corruption problem. The problem is
> that it's a batch job, and the current environment does not allow to
> debug it interactively. So I can only analyze the core file using dbx,
> but it seems the memory was corrupted elsewhere, so the call stack of
> the core file does not help.
> 
> Any idea?
> 
> Thanks!
> 
Check out the AppCrash dtrace program at:
http://developers.sun.com/solaris/articles/app_crash/app_crash.html

-- 
----------------------------------
Randy Jones
E-Mail: randy@jones.tri.net
----------------------------------

> Use Purify from IBM (used to be Rational Software but IBM bought them).
> It is now under the Rational brand at IBM.

I have to submit the job through a batch file. It runs on multiple
processors, and I can't debug it interactively.  Is purify still useful
for me?

Yep, Purify create a new binary that you then run.

hence "I've purified the binary!"

I have used mpatrol to find problems.
..
<david@smooth1.co.uk> wrote in message
news:1126221891.029644.263870@g47g2000cwa.googlegroups.com...
>
> Yep, Purify create a new binary that you then run.
>
> hence "I've purified the binary!"
>

Rich Teer <rich.teer@rite-group.com> wrote:
> On Wed, 7 Sep 2005, Patricia wrote:

>> Seems my parallel program has memory corruption problem. The problem is
>> that it's a batch job, and the current environment does not allow to
>> debug it interactively. So I can only analyze the core file using dbx,
>> but it seems the memory was corrupted elsewhere, so the call stack of
>> the core file does not help.

> Check out libumem and/or the watchmalloc library (see my book, Solaris
> Systems Programming, for more info, and their respective man pages).

Actually your book seems to mention libumem only in a few lines on page 100,
and except for the diagram on page 105, the discussion of watchmalloc
is paraphrased from the Solaris manpages.

(The manpages of course are freely available in a variety of
 searchable media ;-)

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

how about bcheck ?