Обсуждение: Trouble debugging contrib/fulltextindex

Hi All,

Few quick questions.

1. How do you compile contribs with full debugging symbols.  I always get
heuristic-fencepost-blah probs with gdb even though I've configured postgres
with all the debugging stuff.  Makes it really hard to find probs in the
contribs.

2. Should contribs exclusively use palloc/pfree?  I notice that
fulltextindex is using malloc and free - is there any real reason not to
change them?

I've attached the current tarball (extract in contrib) but my regression
test is crashing and I've had to fill it full of elogs to see that nargs is
being overwritten by an overflow or something.

Florian - feel like helping me test/fix it.  go 'gmake install' and then
'gmake installcheck' to test it.

Thanks,

Chris

Christopher Kings-Lynne writes:

> 1. How do you compile contribs with full debugging symbols.  I always get
> heuristic-fencepost-blah probs with gdb even though I've configured postgres
> with all the debugging stuff.

First, compile without optimization (-O0).  Second, using LOAD to load the
shared object before the function call may be of advantage.  I would allow
you to set breakpoints in the loaded object, for example.  Just waiting
for the code to crash and hoping to get a good backtrace isn't always a
successful strategy.

> 2. Should contribs exclusively use palloc/pfree?

Yes (unless there are some wildly unusual memory allocation requirements).

-- 
Peter Eisentraut   peter_e@gmx.net