[pgrouting-dev] dealing with memory issues in home developed code

pgRouting pgrouting-dev
1

I seem to have a memory issue in some code I am writing for c/c++ pg-route project. From the way that the code is behaving I seem to have a memory heap/corruption problem. Is there an easy way of using something like the electric fence or other memory checker on a pg route module or does the entire postgres database need to be recompiled?
Dave.

2

On Tue, Sep 24, 2013 at 08:26:45AM +0200, Dave Potts wrote:

I seem to have a memory issue in some code I am writing for c/c++
pg-route project. From the way that the code is behaving I seem to
have a memory heap/corruption problem. Is there an easy way of
using something like the electric fence or other memory checker on a
pg route module or does the entire postgres database need to be
recompiled?

No need to recompile, check out

But if you're not afraid of recompiling, consider also this one:
http://wiki.postgresql.org/wiki/Valgrind

--strk;

3

On 24/09/13 11:03, Sandro Santilli wrote:

On Tue, Sep 24, 2013 at 08:26:45AM +0200, Dave Potts wrote:

I seem to have a memory issue in some code I am writing for c/c++
pg-route project. From the way that the code is behaving I seem to
have a memory heap/corruption problem. Is there an easy way of
using something like the electric fence or other memory checker on a
pg route module or does the entire postgres database need to be
recompiled?

No need to recompile, check out
http://blog.cleverelephant.ca/2008/08/valgrinding-postgis.html

But if you're not afraid of recompiling, consider also this one:
http://wiki.postgresql.org/wiki/Valgrind

Thanks Sandro, got it sorted.

--strk;
_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev