>> Shouldn't escarg[] contain a nul-terminated string?
>
> Yes, I wondered that too when I looked at it again later. In which
> case the code ought to be safe.
> But if it's true that escarg[] should always be a nul-terminated
> string (are you confident of this? I haven't studied the code to
> check where it comes from), then I'd agree that this appears to
> point to a bug in the caller rather than in sqlite itself.
Not as confident as I was the other day. Now fixed here:
http://www.sqlite.org/src/info/9abd6aa831
Thanks for tracking this down.
Dan.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users