[compiler-rt] r267084 - Enable stack-use-after-scope tests.

[Dimitry Andric via llvm-commits]

I think source file + line number should probably work.  Or if FileCheck supports alternate expressions, we could supply both the mangled and unmangled form of the operator?

-Dimitry

> On 01 May 2016, at 22:16, Evgenii Stepanov <eugeni.stepanov at gmail.com> wrote:
> 
> Would it work if the test matched source file name + line number,
> without the function name?
> I think there were symbolization problems on Windows, too, in this test.
> 
> On Sun, May 1, 2016 at 11:00 AM, Ed Maste <emaste at freebsd.org> wrote:
>> On 1 May 2016 at 15:42, Dimitry Andric <dimitry at andric.com> wrote:
>>> 
>>> That said, stack frame 0 has a call to '_ZZ4mainENK3$_0clEv', which translates to 'main::$_0::operator()() const', but for some reason llvm-symbolizer fails to demangle this identifier.  Any idea what might be wrong?
>> 
>> I suspect llvm-symbolizer is using the system's demangler
>> (__cxa_demangle in libcxxrt), and it is missing support for some
>> mangled name constructs.
>> 
>> Upstream bug reports are:
>> https://github.com/pathscale/libcxxrt/issues/11
>> https://sourceforge.net/p/elftoolchain/tickets/508/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160502/e9dcf22a/attachment.sig>