This seems to be working. I put it up for review here, Tamas:
http://reviews.llvm.org/D13777
On Thu, Oct 15, 2015 at 9:03 AM, Todd Fiala wrote:
> I'm re-running the tests to make sure, but I think that fixed it. I had
> always seen it at least once on test runs locally, but didn't see it on t
I'm re-running the tests to make sure, but I think that fixed it. I had
always seen it at least once on test runs locally, but didn't see it on the
last one.
On Thu, Oct 15, 2015 at 8:10 AM, Todd Fiala wrote:
> Okay! I'll give that a shot now and report back what I find.
>
> Thanks, Tamas :-)
Okay! I'll give that a shot now and report back what I find.
Thanks, Tamas :-)
-Todd
On Thu, Oct 15, 2015 at 3:37 AM, Tamas Berghammer
wrote:
> Hi Todd,
>
> The 64 bit ID of a DIE is built up in the following way:
> * The offset of the DIE is in the lower 32 bit
> * If we are using SymbolFile
Hi Todd,
The 64 bit ID of a DIE is built up in the following way:
* The offset of the DIE is in the lower 32 bit
* If we are using SymbolFileDWARF then the higher 32 bit is the offset of
the compile unit this DIE belongs to
* If we are using SymbolFileDWARFDwo then the higher 32 bit is the offset
Hi Tamas,
There is an assert in DWARFDIE.cpp (lines 189 - 191) that we're hitting on
the OS X side somewhat frequently nowadays:
assert ((id&0xull) == 0 ||
(cu_id&0xll) == 0 ||
(id&0xull) == (cu_
