[cfe-dev] Announcing "clang-ctags"

[Sean Silva]

I saw the bug report, but that gives only memory addresses and
instruction offsets for what the offending code is (`0x1048b50b1 in
(anonymous namespace)::ASTStatCache::getStat(char const*,
stat&, int*) (in clang-tags) + 977`); given the size of `getStat` and
a brief perusal of the source, it seems like at least one level of
inlining is involved. It would be immensely helpful if you could tie
that address back to the statement/expression which causes the
reference.

--Sean Silva

On Tue, Jul 24, 2012 at 10:18 AM, John Wiegley <johnw at boostpro.com> wrote:
>>>>>> Sean Silva <silvas at purdue.edu> writes:
>
>> If it consistently triggers inside that function, then maybe you could
>> single step it through that function? It's a bit tedious to do 5-11 times,
>> but it will probably find the offending stray memory reference.
>
> I built Clang with ASan, so I know where the reference happens (see bug
> report), I just don't know why it's using a freed memory block.
>
> --
> John Wiegley
> BoostPro Computing
> http://www.boostpro.com
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev