Re: [Firebird-devel] Segfault problem

[Brad P. <br...@li...>]

> this is expected. valgrid doesn't understand how Firebird 1.5 memory
> pools work

Are you sure its right though and that the errors getting spit out are all 
invalid?  I hate when code does things that break memory debuggers like that 
since it makes it hard to find a real problem then with all the noise going 
on.

> > linking with qt-mt and libgds produce non-working executable
>
> There could be several reasons of the problem:
> 1. you are trying to link multi-threaded application with non-mt
> version of client library. you should use libfbclient.so for
> multi-threaded applications, not libfbembed.so (installed and linked
> to libgds.so for Linux CS by default)

The RPM package I installed didn't install any fbclient library!  I installed 
FirebirdCS-1.5.0.3780-RC6.rpm so it is as far as I know the latest CS version 
for Linux available.  Is there supposed to be a libfbclient.so somewhere?

As someone else on the list already showed though, the problem also happens if 
you just link with libstdc++ and libgds in that order for a very simple 
program that certainly doesn't use threads so I don't think threads come in 
to it.

> 2. QT re-defines some global symbol and this conflicts with Firebird
> client library. This may be fixed and I'll need more info or SSH root
> access to your machine to resolve the problem (as I do not have RH9
> nearby).

Again as shown on the list you don't even need to use Qt.  Just try the 
example program I listed using "-lstdc++ -lgds" and see if it segfaults for 
you.  Shouldn't matter that its RH9 either since the other person was testing 
with RH8 and I imagine it will happen with other distributions.

-- 
Brad Pepers
br...@li...