[llvm-bugs] [Bug 48497] New: Segfault with odd template

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=48497

            Bug ID: 48497
           Summary: Segfault with odd template
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: harlan.connor+llvm at gmail.com
                CC: blitzrakete at gmail.com, dgregor at apple.com,
                    erik.pilkington at gmail.com, llvm-bugs at lists.llvm.org,
                    richard-llvm at metafoo.co.uk

Created attachment 24279
  --> https://bugs.llvm.org/attachment.cgi?id=24279&action=edit
The original source, clang++ output, preprocessed source and run script

I was writing a class registry macro, and accidentally picked the same name for
my lambda argument as the registered class. With g++, this gives a compiler
error, but for clang++ (since at least 6.0), it segfaults.

I have split the statements into three groups. Each one acts as described in
isolation, or as part of a whole.

I rather confident that this isn't exploitable. This appears to be a null
pointer dereference rather than anything more scary, and after half an hour of
poking around, I couldn't get anything out of it. So I get that this is not a
*huge* priority, as the code itself is not well-formed, but clang probably
shouldn't explode like this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20201213/9f7aed60/attachment-0001.html>