On Fri, 2007-10-19 at 14:52 +1000, Ian Holsman wrote: > yes thats' debugging, but it would be nice to be able to return the > error message when it fails to connect. the 'close' after the real_open > removes the error so all you get is the internal error code.
Yeah, that's been the problem of the 1.2 API. In 1.3, we cannot do it with the same function (API/ABI backward compatibility), but we can introduce another function (e.g. apr_dbd_open_ex()) that does return an error. > interesting, on OS/X it gets one every time, even running it with -X. > (when i specify the groups=xyz in the DBDParam setting) Your fix has now been committed to both the trunk and 1.2.x, so hopefully you won't see those segfaults again :-) -- Bojan
