On Sat, Dec 21, 2013 at 1:25 PM, jitendar kumar <jitenda...@gmail.com>wrote:
> Dear SQLITE users,
>
> As we know SQLITE source code has about 200 instances of memcpy usage.
>
> When we use the query " select * from tablename" from application , memcpy
> in function sqlite3ExprAlloc has value memcpy (dest *0x5637, src *NULL, n
> 0).
Are you talking about this memcpy:
http://www.sqlite.org/src/artifact/ffe4bc79c6?ln=437
Notice also the assert() statement on the previous line.
>
> This gives an alarm with a memory debugger tool "DUMA" that we use to catch
> direct unintended memory access in source code.
>
> I have tried testing many sql queries but practically found the result when
> src =NULL , length is always 0.
>
> Please help confirming this :
> " Is there any other possible scenario in which values passed to any memcpy
> in source code could ever have value src =NULL and length != 0 " ???
> or
> " Is SQLITE safe from any scenario where memcpy can have values src = NULL
> and length != 0 " ???
>
> Looking forward to your valuable suggestions .
>
> Thanks in advance.
>
> Regards,
> Jitendar Kumar
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
