Does someone know why _ast_strdup calls calloc instead of malloc? I found this in one of my recent stack traces: #5 0x0819100b in _ast_calloc (n_obj=1, s_obj=95) at /home/irek/tstastdbg/src/lib/libast/vmalloc/malloc.c:496 #6 0x0814eb76 in _ast_strdup (s=0xffffbf9b "/home/irek/tstastdbg/arch/linux.i386/bin/ksh")
Does doesn't sound sane because the memory used to duplicate the string is filled anyway, the bzero used by calloc is therefore an overkill. Irek _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
