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: unassignedclangb...@nondot.org
Reporter: harlan.connor+l...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@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._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
