Alan DeKok <aland@deployingradius.com> wrote:
This is a different implosion this time round to your last one. Looks like Alan's SQL patch simply postponed the SIGSEGV to a different part of the code. Not sure what should be done, but it looks like errorcode also needs to be changed (probably set to NULL explicitly or something). Alternatively it might be that the error code table in sql_postgresql.h needs updating? No real idea here, Alan?
I'd suggest changing sql_query() function in sql_postgresql.c to:
... if (!errormsg) return -1; ...
instead of the current block of code { errormsg = "FATAL ERROR" }
As Duarte is so able to reproduce this bug I guess this is over to him? Cheers -- Alexander Clouter .sigmonster says: Cure the disease and kill the patient. -- Francis Bacon