Hi all,
I pulled in recent changes to upstream llvm, clang and lldb and it seems
to have tipped my windows build over the edge, and its complaining that
my object files have exceeded the section limit.
This error is raised while building the clang libraries. Has anyone
else seen this problem whi
Hiya everyone,
I was wondering if anyone knows about the status of inspecting macros
for objects compiled with clang.
Using either the DWARF 5 .debug_macro section or DWARF 4 .debug_macinfo
section.
We can debug macros from gcc with -g3, but I can't seem to get clang to
emit anything lldb ca
Which object file has crossed the limit? When this has happened before,
this has usually highlighted over use of templates, which is worth fixing
because it speeds up builds on other platforms as well. If MSVC 2015
instead just happens to generate say one extra section per function, then
we should
Hi Reid,
Thanks for taking a look at this.
Here was the full error:
llvm\tools\clang\lib\ASTMatchers\Dynamic\Registry.cpp : fatal error C1128:
number of sections exceeded object file format limit: compile with /bigobj
That file seems to have quite a bit of macro magic going on, so I'll try
to
You should ask on a clang list for a 100% correct answer, but I am pretty sure
clang does not support macro information. You can get somewhat the same result
by building clang modules and importing them into lldb. But you can't build
modules for C++ yet, so you can only do this for C & ObjC pr
OK, we've had to change that several times now. At this point I think we
should just enable bigobj on that specific file. I'll try to prepare a
patch.
On Tue, Feb 9, 2016 at 9:52 AM, Aidan Dodds wrote:
> Hi Reid,
> Thanks for taking a look at this.
> Here was the full error:
>
> llvm\tools\clang
I've been away from LLDB development for a little while but am
starting to work on it again.
I used to run a few tests using dotest.py's -f or -p flags, but they
don't seem to be working now.
-f filterspec Specify a filter, which consists of the test class
name,
Try passing the directory to start in as the last argument. Also make sure
you include .py on the filename when using -p (I don't actually know if
this is required but I do it).
% python dotest.py
--executable /tank/emaste/src/llvm/build-nodebug/bin/lldb -C /usr/bin/clang
-v -t -p TestCppIncomple
Zachary's solution will work as well but that one won't make debugging the
test too easy (still using several processes). If you want to run just 1
test then you have to specify --no-multiprocess and then you can use the
same flags as before (-p, -f)
On Tue, Feb 9, 2016 at 10:19 PM Zachary Turner
On 9 February 2016 at 17:19, Zachary Turner wrote:
> Try passing the directory to start in as the last argument. Also make sure
> you include .py on the filename when using -p (I don't actually know if this
> is required but I do it).
>
> % python dotest.py --executable /tank/emaste/src/llvm/buil
I’ve been investing the “po performance bug” ( po when
debugging Xcode is extremely slow) in recent Xcode, and I discovered this
problem.
We are looking at pch files that are generated on Xcode’s behalf and it looks
like we’re recursing through their dependencies when we don’t find something,
11 matches
Mail list logo
