--- layout: fc_discuss_archives title: Message 7 from Frama-C-discuss on July 2018 ---
Here it is: frama-c -main main -verbose 3 -machdep gcc_x86_64 -c11 -cpp-frama-c-compliant $SRCS -cpp-extra-args="-I. -I/data/nginx-1.9.14/src/http -I/data/nginx-1.9.14/src/http/modules -I/data/nginx-1.9.14/src/mail -I/data/nginx-1.9.14/src/stream -I/usr/include/openssl -I/data/nginx-1.9.14/objs -I/data/nginx-1.9.14/src/os/unix -I/data/nginx-1.9.14/src/core -I/data/nginx-1.9.14/src/event -D NGX_HAVE_SCHED_SETAFFINITY -DSSL_CTRL_SET_TLSEXT_TICKET_KEY_CB" -impact-pragma ngx_alloc -impact-print -no-val-alloc-returns-null On Wed, Jul 4, 2018 at 2:31 PM, Virgile Prevosto <virgile.prevosto at m4x.org> wrote: > > > 2018-07-04 15:21 GMT+02:00 Divya Muthukumaran <divya84 at gmail.com>: > >> Thanks, when I change the declaration from void *(void) to void *() I >> don't get that error anymore. >> >> I am not encountering an error saying -- >> >> [kernel:annot:missing-spec] src/os/unix/ngx_errno.c:67: Warning: >> >> Neither code nor specification for function strlen, generating default >> assigns from the prototype >> >> [value] src/os/unix/ngx_errno.c:67: builtin Frama_C_strlen: invalid base: >> NULL >> >> >> I had assumed that Frama-C automatically uses its own specfication for >> libc functions such as strlen, so why do I get that complaint? >> >> > This is indeed normally the case. Can you give us the exact command line > that you're using to launch Frama-C? > > Best regards, > -- > E tutto per oggi, a la prossima volta > Virgile > > _______________________________________________ > Frama-c-discuss mailing list > Frama-c-discuss at lists.gforge.inria.fr > https://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20180704/162f9c9b/attachment-0001.html>