Libérer l'espace memoire des messages d'erreurs? [Résolu]

[sofiane80]

Bonjour tout le monde,

Après avoir executer la fonction

Code :

sqlite3_exec( sqlite3* db ,const char *sql,  int (*callback)(void*,int,char**,char**), void *,  char **errmsg);

, ou toutes autre fonction qui utilise le char ** errmsg ,doit-on libéré le errmsg ?

MERCI.

[bigane]

Salut Sofiane80,

Voici un post sur la liste de diffusion SQLite (05/07/2006) qui répond à ta question :

xxxxxxxrger@faa.gov wrote:
> > A few quick questions...
> >
> > If an error is returned by sqlite3_exec( ) , I believe the error message is
> > written in the (char **errmsg) provided in the 5 parameter of the function
> > call.
> >
> > 1. Is this the same error text that can be obtained by
> > sqlite3_errmsg( ) ?

Maybe or maybe not. The error message returned by sqlite3_exec()
might be more detailed. Depends on the error.

> > 2. If this is the same error text that can be obtained by
> > sqlite3_errmsg( ), what happens if I call sqlite3_free( ) before
> > sqlite3_errmsg( )?
> >

By "the same" I mean the same sequence of bytes. The error message
from sqlite3_exec() is always obtained from a malloc-like memory
allocator and must be freed using sqlite3_free(). The error message
returned by sqlite3_errmsg() is always a constant, static string.
The error messages might say the same thing, but they are distinct
strings.
--
D. Richard Hipp

La réponse de D. Richard Hipp est : oui, il faut libérer la mémoire :
" must be freed using sqlite3_free()"

a+