Subject gbak segmentation fault
Author I think thats obvious :)
I've searched around for this on google groups and also through this
archive but don't see the answer jumping out at me. I've put
together a new Linux box with RH ES3.3 and Firebird 1.5.2.xxx.rpm
from sourceforge and everytime I go to restore a database, gbak
restores to a point, then has a Segmentation Fault and quits. I've
tried different databases which are being used on other running
systems so I know the databases are not corrupt. The other systems
are running RH ES3.0 and Firebird 1.5.0.xxx.rpm, so I loaded 1.5.0
onto this system, but still get the same results. I have a
suspicion it could be RH 3.3 causing the problem, where the others
are 3.0, but I don't really have anything to prove it, and I would
think if there was a major problem with the RPM install rpm would
warn or quit out if dependency issues were causing all this. Does
anyone have an idea of what I might try to even find out what the
problem is? Any help would be appreciated. Thanks in advance.

Obvious things like disk space, permissions, have been checked.
What really doesn't make sense is that it even writes anything.
Each database file I try to restore does not quit at the same size
as other database files. But each database file I restore does quit
at the same size as the previous try of that specific file, if that
makes sense.

Anyway, hope someone can help. Thanks...