search for: mallochelp

...: unable to start device pdf In addition: Warning message: cannot open `pdf' file argument `hi.pdf' *** malloc[477]: Deallocation of a pointer not malloced: 0x143cf5c0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug _ platform powerpc-apple-darwin6.8 arch powerpc os darwin6.8 system powerpc, darwin6.8 status major 2 minor 0.0 year 2004 month 10 day 04 language R > sessionInfo() R version 2.0.0, 2004-10-04, powerpc-apple-darwin6.8 attach...

I got a problem with UL followed by by OL when I using perl module "Text-Markdown-1.0.5". I wrote the following markdown code. - a - b 1. 1 2. 2 I expected that Text-Markdown would produce the following HTML. <ul> <li>a</li> <li>b</li> </ul> <ol> <li>1</li> <li>2</li> </ol> However, "Text-Markdown-1.0.5"

...t the following on console: rock/j_geils_band/showtime@st1100% xmms 01-jus_cant_stop_me.flac *** malloc[19338]: Deallocation of a pointer not malloced: 0x13a5aec; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug It looks like someone has reported this same bug under FreeBSD. It hasn't seemed to cause me any problems so far. Now onto my actual useful bug report that i haven't seen before... 3) To get the xmms plugin shared library to build properly, i had to hack the...

...-fno-builtins. I don't believe that isMalloc is bogus, just that llvm does not support the ability to turn it off. Here is some previous discussion about this topic: On Sep 11, 2009, at 11:30 AM, Chris Lattner wrote: > On Sep 11, 2009, at 10:22 AM, Dan Gohman wrote: > >> If MallocHelper is going to replace MallocInst, how will it support >> -fno-builtins? With MallocInst, one at least had the option of >> omitting the RaiseAllocations pass (though it seems llvm-gcc and >> clang don't actually do this, which is a bug). With MallocHelper, >> how can -f...

Hi Victor, this code from the verifier broke the Ada front-end build: const Module* M = CI.getParent()->getParent()->getParent(); Constant *MallocFunc = M->getFunction("malloc"); if (CI.getOperand(0) == MallocFunc) { const PointerType *PTy = PointerType::getUnqual(Type::getInt8Ty(CI.getParent()->getContext())); Assert1(CI.getType() == PTy, "Malloc

...t; > rock/j_geils_band/showtime@st1100% xmms 01-jus_cant_stop_me.flac > *** malloc[19338]: Deallocation of a pointer not malloced: > 0x13a5aec; This could be a double free(), or free() called with > the middle of an allocated block; Try setting environment variable > MallocHelp to see tools to help debug yes I think this is fixed in CVS. > 3) To get the xmms plugin shared library to build properly, i had to > hack the > libtool-disable-static script to get EGREP from the PATH. There was > a similar > hack for SED in the libtool file with a JEC comment....

...--delete --backup --backup-dir=... I occasionally get the following errors from the Mac OS X malloc(): rsync(486) malloc: *** Deallocation of a pointer not malloced: 0x4aeb54; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug It can be reproduced with dry runs. But if the file system is modifed, it can also go away. The stack trace from where the printout comes (strings replaced with "..."): (gdb) bt #0 0x9012b760 in malloc_printf () #1 0x90005f5c in free () #2 0x00037fd4 in un...