search for: zalloc

...e ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir/utils/$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all ) || exit 1; \ done gmake[2]: Entering directory `/home/myuser/LLVM/objdir/utils/Burg' llvm[2]: Compiling zalloc.c for Release build if gcc -I/home/myuser/LLVM/objdir/utils/Burg -I/home/myuser/LLVM/objdir/../srcdir/utils/Burg -I/home/myuser/LLVM/objdir/../srcdir/include -I/home/myuser/LLVM/objdir/include -I/home/myuser/LLVM/objdir/include -I/home/myuser/LLVM/objdir/../srcdir/include -D_GNU_SOURCE -D__STDC_LI...

I commented this line and it is compiling now: extern void *malloc ARGS((unsigned)); I hope that will not cause a different kind of problem. What it is zalloc used for? Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > It seems that this happened before but I do not know the details: > > http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html > > Yup, this patch shoul...

...ease build llvm[2]: Compiling queue.c for Release build llvm[2]: Compiling rule.c for Release build llvm[2]: Compiling string.c for Release build llvm[2]: Compiling symtab.c for Release build llvm[2]: Compiling table.c for Release build llvm[2]: Compiling trim.c for Release build llvm[2]: Compiling zalloc.c for Release build /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin g types for 'malloc' /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin g types for 'malloc' gmake[2]: *** [/homes/myuser/LLVM/llvmobj/utils/Burg/Release/za...

It seems that this happened before but I do not know the details: http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > llvm[2]: Compiling zalloc.c for Release build > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for 'malloc' > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for 'malloc' > > gmake[2]: ***...

On 11/24/2013 03:29 AM, Gene Cumm wrote: >> >> (Sorry for the top posting.) > > I just started examining this and find it odd that the core_udp_recv() > doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. > All three are a part of commit fe283b78 by Matt Fleming. Should this > be made into a zalloc() rather than pushing it into the stack? It'd > seem like it could run some stack issues plus there's no guarantee > what'...

Greetings, Unbound 1.4.20 OS X 10.8.4 - Server NSD 3.2.15 I have installed 'unbound' and it works nicely on my client (test purpose) - Client is MacBook Air. I have installed NSD (will be in replacement of BIND) on said client. All is good but when i try to start NSD Error --> nsd can't bind udp socket: address already in use. Everything is configured to bind to 127.0.0.1. #

>I played around with the udp4_cb function and it looked like it was coming back with token->Status == 512, which (if I read the spec right) isn't a valid value. I'm not sure what is coming through on that. I changed the if to if (token->Event) { cb_status = 0; } Looks like the same thing with tcp.c. After I changed that callback, everything went through and I go into the OS

...-- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > I commented this line and it is compiling now: > > > > extern void *malloc ARGS((unsigned)); > > > > I hope that will not cause a different kind of problem. What it is zalloc used for? > > zalloc is part of Burg, which is used by the Sparc backend. I strongly > suggest adding '#include <stdlib.h>' to that file as well. > > -Chris > > > --- Chris Lattner <sabre at nondot.org> wrote: > >> On Sat, 12 Mar 2005, xavie...

...t;> >> But, if I go back to 1 subnet after those changes, it errors out with >> Invalid Parameter when attempting to send the first packet. >> >> (Sorry for the top posting.) > > I just started examining this and find it odd that the core_udp_recv() > doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. > All three are a part of commit fe283b78 by Matt Fleming. Should this > be made into a zalloc() rather than pushing it into the stack? It'd > seem like it could run some stack issues plus there's no guarantee > what'...

On Tue, Nov 26, 2013 at 2:02 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 11/24/2013 03:29 AM, Gene Cumm wrote: >>> >>> (Sorry for the top posting.) >> >> I just started examining this and find it odd that the core_udp_recv() >> doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. >> All three are a part of commit fe283b78 by Matt Fleming. Should this >> be made into a zalloc() rather than pushing it into the stack? It'd >> seem like it could run some stack issues plus there's no guarantee &...

...ata, NULL, NULL, NULL); - if (status != EFI_SUCCESS) - Print(L"Failed to get UDP mode data: %d\n", status); - else - socket->net.efi.localport = udata.StationPort; + + b = efi_create_binding(&Udp4ServiceBindingProtocol, &Udp4Protocol); + if(!b) + return -1; + + udp_io=zalloc(sizeof(UDP_IO)); + if(!udp_io) + goto bail; + + udp_io->b = b; + + udp = (EFI_UDP4 *)b->this; + udp_io->Protocol_Udp4 = udp; + + socket->net.efi.context = udp_io; + + // + // Create the timer used to time out transmit, receive, and get map events + // + status = uefi_call_wrappe...

...t;, 6)) { opt.loadfile = argv[i] + 6; opt.grldr = true; @@ -1583,8 +1589,30 @@ int main(int argc, char *argv[]) } if (opt.grub) { + char *path; regs.ip = 0x200; /* jump 0x200 bytes into the loadfile */ + /* 89 bytes reserved for menu at offset 0x217 */ + path = zalloc(89); + + if (path && opt.grubmenu) { + char partition[5]; /* maximum is ",100" and up! */ + int len; + + if (whichpart > 1) + sprintf(partition, ",%d", whichpart - 1); + else + partition[0] = '\0'; + sprintf(path, "(%cd%d%s)/", +...

...I go back to 1 subnet after those changes, it errors out with >>> Invalid Parameter when attempting to send the first packet. >>> >>> (Sorry for the top posting.) >> >> I just started examining this and find it odd that the core_udp_recv() >> doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. >> All three are a part of commit fe283b78 by Matt Fleming. Should this >> be made into a zalloc() rather than pushing it into the stack? It'd >> seem like it could run some stack issues plus there's no guarantee &...

...e file /usr/src/sys/vm/vm_object.c looks like: > 232 vm_object_t > 233 vm_object_allocate(type, size) > 234 objtype_t type; > 235 vm_size_t size; > 236 { > 237 vm_object_t result; > 238 > 239 result = (vm_object_t) zalloc(obj_zone); > 240 > 241 _vm_object_allocate(type, size, result); > 242 > 243 return (result); > 244 } A number of users appear to be encountering an error in which the zalloc() appears to be returning NULL, instead of hanging until the sun goes nova like i...

...SwfdecDecoder *dec = SWFDEC_DECODER (s); z_stream *z; int ret; + guint8 *data; + data = g_try_malloc (dec->bytes_total - 8); + if (data == NULL) + return FALSE; + s->uncompressed_buffer = swfdec_buffer_new_for_data (data, dec->bytes_total - 8); z = &s->z; z->zalloc = zalloc; z->zfree = zfree; ret = inflateInit (z); SWFDEC_DEBUG ("inflateInit returned %d", ret); - s->uncompressed_buffer = swfdec_buffer_new_and_alloc (dec->bytes_total - 8); z->next_out = s->uncompressed_buffer->data; z->avail_out = s->uncompre...

...h and I go into the OS install. > > But, if I go back to 1 subnet after those changes, it errors out with > Invalid Parameter when attempting to send the first packet. > > (Sorry for the top posting.) I just started examining this and find it odd that the core_udp_recv() doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. All three are a part of commit fe283b78 by Matt Fleming. Should this be made into a zalloc() rather than pushing it into the stack? It'd seem like it could run some stack issues plus there's no guarantee what's in it (unless the...

Hi I am trying to build the llvm tools following the instructions here: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html But I get this error: /zalloc.c:9: error: conflicting types for 'malloc' I am using gcc 3.4.1 What can be the problem? __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/

The variable 'ok' is never used and generates a warning. Remove it. Also ntfssect.c is designed to be compiled in non Unicode mode when using MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use of 'A' API calls) so that it doesn't break when compiled in Unicode mode, which is what Rufus uses with MSVC. -------------- next part --------------

...le index c5b1981..50fd07f 100644 --- a/com32/lib/Makefile +++ b/com32/lib/Makefile @@ -25,7 +25,7 @@ LIBOBJS = \ strtoimax.o strtok.o strtol.o strtoll.o strtoul.o strtoull.o \ strtoumax.o vfprintf.o vprintf.o vsnprintf.o vsprintf.o \ asprintf.o vasprintf.o strlcpy.o strlcat.o \ - vsscanf.o zalloc.o \ + vsscanf.o zalloc.o hexdump.o \ \ opendir.o readdir.o closedir.o getcwd.o chdir.o fdopendir.o \ \ diff --git a/com32/lib/hexdump.c b/com32/lib/hexdump.c new file mode 100644 index 0000000..04edbcf --- /dev/null +++ b/com32/lib/hexdump.c @@ -0,0 +1,42 @@ +/* + * The hex dump lib....

...d *addr) g_free (addr); } -static void * -lossless (void *zptr, int zlen, int *plen) +static guint8 * +lossless (const guint8 *zptr, int zlen, int len) { - void *data; - int len; - z_stream *z; + guint8 *data; + z_stream z = { NULL, }; int ret; - z = g_new0 (z_stream, 1); - z->zalloc = zalloc; - z->zfree = zfree; - z->opaque = NULL; - - z->next_in = zptr; - z->avail_in = zlen; - - data = NULL; - len = 0; - ret = inflateInit (z); - while (z->avail_in > 0) { - if (z->avail_out == 0) { - len += 1024; - data = g_realloc (data, len); -...