Re[2]: [firebird-devel] Firebird 1.5 segfault

[Nickolay S. <sk...@bs...>]

Hello, Brad,

> Also it sounds like the client library isn't even supposed to be using the
> memory pool and also the valgrind output shows that things aren't right even
> when I do link things in the right order.  I think things are rotten in here
> and need to be fixed!

1. valgrind is not supposed to work with Firebird 1.5. It doesn't
understand hierarchical pools sub-allocation (this may be worked
around, but in tool-dependent way, this will partly be solved in
Firebird 2.0).
2. there is no substantial difference between server engine and client
library. For example, when you link to libfbembed.so you actually link
to full-fledged embeeded server engine.

The strategic mistake was usage of STL objects in Firebird memory
pools (this forces us to re-define global delete). The fix is in
progress in FB2.0 tree (all needed classes are implemented and are
just pending to replace STL analogs).

I'll take a look at FB1.5 codebase and will recon what can be done
there with this problem. And yes, this is the real problem.

> Brad Pepers

-- 
Nickolay Samofatov                        mailto:sk...@bs...