On Mar 6, 2008, at 10:57 AM, Kenneth LO wrote:

> In previous versions (<=3.4.10) I use to do if (errmsg) { free(errmsg)
> ; } without problem.
>
> In 3.5.6 the free() will segfault (yes, even after if) with a "invalid
> pointer" message.
>
> It's my old understanding that sqlite3_get_table (previously
> sqlite_get_table) will malloc for *errmsg and I'll need to do the
> free().  Has anything changed?  I'm just recompiling old codes with
> the new lib.

Technically you're supposed to use sqlite3_free(). They might be
different, depending on compilation options.

Dan.





_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to