konrad.trifunovic at gmail.com
Thu Jul 16 15:32:21 CEST 2009
I rather think it is fault of our code, not the PPL one.
What i suspect that there are some memory allocation problems, otherwise
I cannot understand why the crashes are nondeterministic. We actually
do not check for memory allocation faults, so the faults might be
to other places in the code.
What happens is that I'm calling the creation of polyhedron and
deletion of polyhedron
for about 1.000.000 times. Since the code is written in C (we use PPL
C interface), we do not
receive the exceptions that might occur due to failed allocation.
I will first try to do the code that would check if the allocations
failed, so at least
I can stop the graphite myself, and not wait until it crashes randomly...
2009/7/16 Roberto Bagnara <bagnara at cs.unipr.it>:
> Konrad Trifunovic wrote:
>> - the error that I get are random! Yes, that is a nightmare. I suppose
>> it's memory allocation problem (or probably a memory leak). All the
>> errors come from PPL routines. The problem is that sometimes it
>> crashes on 10th invokation of the dependence analyser, sometimes on
>> I would be investigating for a possible memory leak inside dependence
>> analyser (I hope not in PPL).
> Hi Konrad,
> we routinely test PPL with the help of Valgrind, but something may
> of course escape. Please let us know if you narrow down the problem
> to something that is likely to be a bug in PPL.
> All the best,
> Prof. Roberto Bagnara
> Computer Science Group
> Department of Mathematics, University of Parma, Italy
> mailto:bagnara at cs.unipr.it
More information about the PPL-devel