I've built clang/llvm 3.2 from tarballs. My software builds fine with it,
but using the dxr clang plugin dumps core.with the following backtrace:
(gdb) bt
#0 0x003c73832885 in raise () from /lib64/libc.so.6
#1 0x003c73833fed in abort () from /lib64/libc.so.6
#2 0x003c7386f977 in
Yes, I'm using 3.2 and so are the automated tests. Is there any useful
error message printed out before this? Does running with the environment
variable MALLOC_CHECK_=3 make any difference?
Have you tried rebuilding the DXR plugin?
--
James Abbatiello
On Fri, Feb 8, 2013 at 1:49 PM, Chris
On Fri, Feb 8, 2013 at 1:52 PM, James Abbatiello abb...@gmail.com wrote:
Yes, I'm using 3.2 and so are the automated tests. Is there any useful
error message printed out before this?
No. No error messages.
Have you tried rebuilding the DXR plugin?
Yes. And no.
So, I found the
The tree was reorganized in
https://github.com/mozilla/dxr/commit/20db8711737ad4c63bfd8b4028220cd1c4445c56,
moving the plugins directory.
Hopefully you should no longer need dxrroot, plugin_folder, or template
parameters in your config file and they should automatically default to the
right
That's what's strange...git status doesn't complain about the plugins
directory in the old location. In fact, I can do a git log in that
directory and get stuff from as recently as Jan 15.
My mistake. My guess is that git, which tracks only files, doesn't bother with
that plugins dir if it
I guess the take-away lesson is that when doing a re-org of the tree, there
needs to be some out-of-band way to communicate to anyone who may have a
clone to perform a clean.
I'll be sure to post about that and stick it in the (coming soon) changelog in
the future. Sorry to had to chase
