[Users] postgres and long AVPs values BUG?
JF
jfkavaka at gmail.com
Fri Jan 27 18:28:43 CET 2006
Hi,
I increased the length of the value column in the usr_preferences
table from 128 to 1024, but I got a core dump after these logs:
0(24138) val2str(): converting record_route, 12
0(24138) PG[224] str2valp got string
<sip:10.112.64.59;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.12;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.12;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.59;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>
Segmentation fault (core dumped)
This was caused by an avp_db_load() call from the script. I'm using
OpenSER 1.0.0.
I found the following comment on modules/postgres/db_res.c that might
have something to do with it:
/* I'm not sure about this */
/* PQfsize() gives us the native length in the database, so */
/* an int would be 4, not the strlen of the value */
/* however, strlen of the value would be easy to strlen() */
Also, in modules/postgres/db_val.c, there is a FIXME in val2str()
function that seems to be related.
Can anyone help solve this problem? It seems like a bug.
Thanks,
JF
More information about the Users
mailing list