Problem with VADS memory management - any way to tune fat_heap_global?

Problem with VADS memory management - any way to tune fat_heap_global?

[Andreas Schulz]

Maybe someone can enlighten me...
Up to now, I have encountered a few cases where different
programs, all built with VADS 6.3.4(c) (or was it 6.4.3?)
for Solaris 2.6 worked fine until confronted with larger 
amounts of data, where they either exit with an exception
(which is caught internally resp. has escaped my memory, 
so I can't tell exactly which) from, or, if this exception is
ignored, hangup inside some 'fat_heap_global' package
(judging from a core dump analysis).

I'm inclined to try some tweaking with v_usr_conf, since
the problem to me looks like a fragmentation problem
of some limited memory pool, but the VADS reference isn't
very helpful to me in this case...

TIA, A.Schulz

Re: Problem with VADS memory management - any way to tune fat_heap_global?

[Andreas Schulz]

Andreas Schulz <accot.schulz@nord-com.net> wrote:
> programs, all built with VADS 6.3.4(c) (or was it 6.4.3?)

Correction : it's VADS 6.2.3(c)

--
Please reply by group - I don't read this mail regularly


Sent via Deja.com http://www.deja.com/
Before you buy.

Never mind - solved it (was Re: Problem with VADS ...)

[Andreas Schulz]

Problem was in fact a bad exception handler, causing
some low-level exception being propagated to a high-level
procedure - though I'd still like to know why this apparently
messed up dynamic storage..

--
Please reply by group - I don't read this mail regularly


Sent via Deja.com http://www.deja.com/
Before you buy.