search for: _glibcxx_debug

So far we've tracked down four bugs using _GLIBCXX_DEBUG, all of them quite subtle and some of them leading to serious problems like heap corruption. But we've also discovered that compile time can skyrocket in some cases as the library does its checks. The standard library complexity guarantees don't apply with _GLIBCXX_DEBUG. Therefore, we...

Hi, I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to see what would happen, and it's been a complete disaster. The major problem is the use of this API: new CallInst(V, &Args[0], Args.size()); repeated throughout LLVM. When Args is empty, Args[0] is invalid, even if the next operation is taking the address. Tr...

On Sun, 1 Jul 2007, Nick Lewycky wrote: > I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to > see what would happen, and it's been a complete disaster. > > The major problem is the use of this API: > > new CallInst(V, &Args[0], Args.size()); > > repeated throughout LLVM. When Args is empty, Args[0] is invalid, even > if the next...

Do the buildbots build debug compilers? I just updated and yet again we have a bug caught by _GLIBCXX_DEBUG (--enable-expensive-checks). Can we add some builds with --enable-expensive-checks so we catch these problems sooner? -Dave

Nick Lewycky <nicholas at mxc.ca> writes: > Hi, > > I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to > see what would happen, and it's been a complete disaster. > > The major problem is the use of this API: > > new CallInst(V, &Args[0], Args.size()); Forgive me if I'm missing something, but why is it assumed that &Args[0] must be a poin...

I'm reposting this patch at the request of Evan. It fixes a problem with std::priority_queue and _GLIBCXX_DEBUG. -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: schedule_dag.diff Type: text/x-diff Size: 7731 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080229/14bf0bec/at...

I'm continuing my quest to integrate _GLIBCXX_DEBUG into the config system. I now have things at a point where I can configure llvm to build with -D_GLIBCXX_DEBUG and the llvm-gcc will pick up the correct CPPFLAGS automatically. One thing I noticed in the llvm Makefile.rules is this: # If DISABLE_ASSERTIONS=1 is specified (make command line or co...

...:SUnit*, std::allocator<llvm::SUnit*> > >, _Compare = <unnamed>::td_ls_rr_sort]': Missing a patch? Evan On Feb 29, 2008, at 1:40 PM, David Greene wrote: > I'm reposting this patch at the request of Evan. It fixes a problem > with > std::priority_queue and _GLIBCXX_DEBUG. > > -Dave > <schedule_dag.diff>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...make does not add correct options in llvm-config. Best regards, Luba 2012/11/21 Luba Tang <lubatang at gmail.com> > Hi, Kito, > > Did you ever use --enable-expensive-checks when you configure LLVM? > > ${LLVM_BUILD}/configure --enable-expensive-checks > > or > > _GLIBCXX_DEBUG > > is in your environment? > > This will enable RTTI for LLVM > > > 2012/11/21 Kito Cheng <kito at 0xlab.org> > >> > Hi, Kito, >> > >> > I check the trunk r168413, `llvm-config --cxxflags' shows >> > -I/Users/lubatang/SysRoot/in...

Hi David, On Mon, 2007-06-25 at 17:43 -0500, David A. Greene wrote: > I'm continuing my quest to integrate _GLIBCXX_DEBUG into the config system. > I now have things at a point where I can configure llvm to build with > -D_GLIBCXX_DEBUG and the llvm-gcc will pick up the correct CPPFLAGS > automatically. Okay. > > One thing I noticed in the llvm Makefile.rules is this: > > # If DISABLE_ASSERTI...

Hi, I'm trying to write custom pass. However opt started crashed in opt.cpp. After debugging it looks like PassInf->NormalCtor points to unmapped memory (rest of struct contains correct data about my pass) - it pointed high in user memory (0x756e672e006e6f69). It happens only when I tried to install debug version of llvm system-wide (I've check that it wasn't caused by stale .a

On Monday 02 July 2007 16:26, Chris Lattner wrote: > On Sun, 1 Jul 2007, Nick Lewycky wrote: > > I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to > > see what would happen, and it's been a complete disaster. Well, that's a bit harsh, isn't it? It's finding bugs, just like it's supposed to. :) I believe I've started to run into this one too. I hit a similar error and was in the mi...