search for: freep

...uld be nice to use AC_COMPILE_IFELSE here, but gcc just +dnl emits a warning for attributes that it doesn't understand. +AC_MSG_CHECKING([if __attribute__((cleanup(...))) works with this compiler]) +AC_RUN_IFELSE([ +AC_LANG_SOURCE([[ +#include <stdio.h> +#include <stdlib.h> + +void +freep (void *ptr) +{ + exit (0); +} + +void +test (void) +{ + __attribute__((cleanup(freep))) char *ptr = malloc (100); +} + +int +main (int argc, char *argv[]) +{ + test (); + exit (1); +} +]]) + ],[ + AC_MSG_RESULT([yes]) + AC_DEFINE([HAVE_ATTRIBUTE_CLEANUP],[1],[Define to 1 if '__attr...

...t; asterisk SIP <=> lan Everythings works fine but sometime I can't get incoming call. here are some of the logs from set debug 25 set verbosity 25 sip show debug and sip.conf and a part of extension.conf thanks in advance Reliably Transmitting (NAT) to 212.27.52.5:5060: OPTIONS sip:freephonie.net SIP/2.0 Via: SIP/2.0/UDP 82.XXX.XXX.XXX:5060;branch=z9hG4bK67c2df66;rport From: "asterisk" <sip:asterisk@82.XXX.XXX.XXX>;tag=as01265eaf To: <sip:freephonie.net> Contact: <sip:asterisk@82.XXX.XXX.XXX> Call-ID: 7263e88c20c9f38c34963cef6704cf07@82.XXX.XXX.XXX CSeq:...

This patch series changes a small part of the library to use __attribute__((cleanup(...))) to automatically free memory when pointers go out of the current scope. In general terms this seems to be a small win although you do have to use it carefully. For functions where you can completely get rid of the "exit code paths", it can simplify things. For a good example, see the

Hi, as it was already discussed on this list, here it is my attempt in splitting virt-p2v in an own repository. Sadly there are things that must be copied from libguestfs, as it cannot be avoided. The approach taken was to run a script (will send separately) to just get the "p2v" subdirectory with its history as own repository, and then add in few followup commits all the bits needed

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a