Bojan Smojver wrote:
apr-util fails like so on FC8:testdbd : -Line 205: failed to fetch driver | Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208899824 (LWP 25720)] apr_dbd_name (driver=0x9ba4a00) at dbd/apr_dbd.c:279 279 { It looks like this is responsible: APU_DECLARE(const char*) apr_dbd_name(const apr_dbd_driver_t *driver) { return driver->name; } Seems driver is NULL. Does this ring any bells for anyone?Could you run this through GDB. That line 205 in testdbd.c looks like this: ------------ ABTS_ASSERT(tc, "failed to fetch driver", rv == APR_SUCCESS); ------------ Not sure how the segfault managed to happen there...
That is run through gdb - it broke during the rpm build (which runs the tests as part of the build), so I am going to have to double check what flags it was built with - I was hoping this would ring some bells.
The code quoted is line 279 of dbd/apr_dbd.c. Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
