13 Jun
2012
13 Jun
'12
11:03 p.m.
Hi Juha,
The second parameter (s2) is allowed to be NULL, but there is no check
that s1->s or s2->s != NULL.
It looks like you have an uninitialised or corrupt value as the first
string, which causes the same problem - segfault
Regards,
Hugh
On 13/06/12 20:14, Juha Heinanen wrote:
Hugh Waite writes:
I see that core_hash has moved from
/lib/kcore/hash_func.h (in 3.2) to
/hashes.h but I think the algorithm is the same one. Maybe pua is
passing a null or uninitialised string?
hugh,
when sending publish, there is two places in pua module where core_hash
is called:
hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE);
and
hash_code= core_hash(publ->pres_uri, NULL, HASH_SIZE);
is it so that the second param cannot be NULL?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev