RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-23 11:13:28 +01:00
Code Issues Projects Releases Wiki Activity
1efce480d9
llvm-mirror/test/Demangle/invalid-manglings.test

227 lines
4.7 KiB
Plaintext
Raw Normal View History

[MS Demangler] Add a regression test for an invalid mangled name. llvm-svn: 349168
2018-12-14 18:59:27 +01:00
; Run llvm-undname with invalid inputs and make sure it doesn't crash.
Fix llvm-undname tests after r358485 llvm-svn: 358487
2019-04-16 15:18:51 +02:00
; RUN: not llvm-undname < %s 2>&1 | FileCheck %s
[MS Demangler] Add a regression test for an invalid mangled name. llvm-svn: 349168
2018-12-14 18:59:27 +01:00
?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__clang@@@Z
; CHECK: ?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__clang@@@Z
; CHECK-NEXT: error: Invalid mangled name
[MS Demangler] Fail gracefully on invalid pointer types. Once we detect a 'P', we know we a pointer type is upcoming, so we make some assumptions about the output that follows. If those assumptions didn't hold, we would assert. Instead, we should fail gracefully and propagate the error up. llvm-svn: 349169
2018-12-14 19:10:13 +01:00
?f0@@YAXPEU?$AS_@$00$$CAD@__clang@@@Z
; CHECK-EMPTY:
; CHECK-NEXT: ?f0@@YAXPEU?$AS_@$00$$CAD@__clang@@@Z
llvm-undname: Fix a crash-on-invalid Found by oss-fuzz, fixes issues 12435 and 12438 on oss-fuzz. Differential Revision: https://reviews.llvm.org/D60202 llvm-svn: 357646
2019-04-04 01:15:56 +02:00
; CHECK-NEXT: error: Invalid mangled name
?@@8
; CHECK-EMPTY:
; CHECK-NEXT: ?@@8
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix an assert-on-invalid Found by oss-fuzz, fixes issues 12428 and 12429 on oss-fuzz. Differential Revision: https://reviews.llvm.org/D60204 llvm-svn: 357647
2019-04-04 01:19:39 +02:00
??
; CHECK-EMPTY:
; CHECK-NEXT: ??
; CHECK-NEXT: error: Invalid mangled name
llvm-undame: Fix an assert-on-invalid Found by oss-fuzz, fixes issue 12432 on os-fuzz. Differential Revision: https://reviews.llvm.org/D60206 llvm-svn: 357648
2019-04-04 01:23:32 +02:00
??0@
; CHECK-EMPTY:
; CHECK-NEXT: ??0@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix a crash-on-invalid Found by oss-fuzz, fixes issue 13260 on oss-fuzz. Differential Revision: https://reviews.llvm.org/D60207 llvm-svn: 357649
2019-04-04 01:27:18 +02:00
? @@ YC@
; CHECK-EMPTY:
; CHECK-NEXT: ? @@ YC@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix more crashes and asserts on invalid inputs For functions whose callers don't check that enough input is present, add checks at the start of the function that enough input is there and set Error otherwise. For functions that return AST objects, return nullptr instead of incomplete AST objects with nullptr fields if an error occurred during the function. Introduce a new function demangleDeclarator() for the sequence demangleFullyQualifiedSymbolName(); demangleEncodedSymbol() and use it in the two places that had this sequence. Let this new function check that ConversionOperatorIdentifiers have a valid TargetType. Some of the bad inputs found by oss-fuzz, others by inspection. Differential Revision: https://reviews.llvm.org/D60354 llvm-svn: 357936
2019-04-08 21:46:53 +02:00
??B@$$J0
; CHECK-EMPTY:
; CHECK-NEXT: ??B@$$J0
; CHECK-NEXT: error: Invalid mangled name
??B@4
; CHECK-EMPTY:
; CHECK-NEXT: ??B@4
; CHECK-NEXT: error: Invalid mangled name
?A?@?@???B@4D
; CHECK-EMPTY:
; CHECK-NEXT: ?A?@?@???B@4D
; CHECK-NEXT: error: Invalid mangled name
?A?@?@???B@4DD
; CHECK-EMPTY:
; CHECK-NEXT: ?A?@?@???B@4DD
; CHECK-NEXT: error: Invalid mangled name
??$A@P15@
; CHECK-EMPTY:
; CHECK-NEXT: ??$A@P15@
; CHECK-NEXT: error: Invalid mangled name
??$A@P
; CHECK-EMPTY:
; CHECK-NEXT: ??$A@P
; CHECK-NEXT: error: Invalid mangled name
?A@@
; CHECK-EMPTY:
; CHECK-NEXT: ?A@@
; CHECK-NEXT: error: Invalid mangled name
?A@@P
; CHECK-EMPTY:
; CHECK-NEXT: ?A@@P
; CHECK-NEXT: error: Invalid mangled name
?A@@4PQA@@
; CHECK-EMPTY:
; CHECK-NEXT: ?A@@4PQA@@
; CHECK-NEXT: error: Invalid mangled name
??__E
; CHECK-EMPTY:
; CHECK-NEXT: ??__E
; CHECK-NEXT: error: Invalid mangled name
??__E@@
; CHECK-EMPTY:
; CHECK-NEXT: ??__E@@
; CHECK-NEXT: error: Invalid mangled name
??__E?Foo@@0HA@@
; CHECK-EMPTY:
; CHECK-NEXT: ??__E?Foo@@0HA@@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix another crash-on-invalid This fixes a regression from https://reviews.llvm.org/D60354. We used to SymbolNode *Symbol = demangleEncodedSymbol(MangledName, QN); if (Symbol) { Symbol->Name = QN; } but changed that to SymbolNode *Symbol = demangleEncodedSymbol(MangledName, QN); if (Error) return nullptr; Symbol->Name = QN; and one branch somewhere returned a nullptr without setting Error. Looking at the code changed in r340083 and r340710 that branch looks like a remnant from an earlier attempt to demangle RTTI descriptors that has since been rewritten -- so just remove this branch. It shouldn't change behavior for correctly mangled symbols. llvm-svn: 358112
2019-04-10 19:31:34 +02:00
??8@8
; CHECK-EMPTY:
; CHECK-NEXT: ??8@8
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix crash on invalid name in a template parameter pointer to member arg Found by oss-fuzz. llvm-svn: 358234
2019-04-12 00:23:35 +02:00
?B@?$?K$H?
; CHECK-EMPTY:
; CHECK-NEXT: ?B@?$?K$H?
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix crash on incomplete virtual this adjusts Found by oss-fuzz. Also remove an else-after-return, this part has no behavior change. llvm-svn: 358237
2019-04-12 00:47:18 +02:00
??C@$
; CHECK-EMPTY:
; CHECK-NEXT: ??C@$
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Don't crash on incomplete enum tag manglings Found by inspection. llvm-svn: 358238
2019-04-12 00:59:25 +02:00
?x@@3PAW
; CHECK-EMPTY:
; CHECK-NEXT: ?x@@3PAW
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix out-of-bounds read on invalid intrinsic function code Found by inspection. llvm-svn: 358239
2019-04-12 01:11:33 +02:00
??}
; CHECK-EMPTY:
; CHECK-NEXT: ??}
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix another crash-on-invalid found by oss-fuzz llvm-svn: 358363
2019-04-15 01:08:12 +02:00
?foo@?$?_
; CHECK-EMPTY:
; CHECK-NEXT: ?foo@?$?_
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix oss-fuzz-foudn crash-on-invalid with incomplete special table nodes llvm-svn: 358367
2019-04-15 01:32:37 +02:00
??_R4
; CHECK-EMPTY:
; CHECK-NEXT: ??_R4
; CHECK-NEXT: error: Invalid mangled name
??_R4foo@@
; CHECK-EMPTY:
; CHECK-NEXT: ??_R4foo@@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix nullptr deref on invalid conversion operator names in template args A ConversionOperatorIdentifierNode has a TargetType which is read when printing it, but if the ConversionOperatorIdentifierNode appears in a template argument there's nothing that can provide the TargetType. Normally the COIN is a symbol (leaf) name and takes its TargetType from the symbol's type, but in a template argument context the COIN can only be either a non-leaf name piece or a type, and must hence be invalid. Similar to the COIN check in demangleDeclarator(). Found by oss-fuzz. llvm-svn: 358421
2019-04-15 18:42:44 +02:00
?foo@?$?BH@@QAEHXZ
; CHECK-EMPTY:
; CHECK-NEXT: ?foo@?$?BH@@QAEHXZ
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix nullptr deref on invalid structor names in template args Similar to r358421: A StructorIndentifierNode has a Class field which is read when printing it, but if the StructorIndentifierNode appears in a template argument then demangleFullyQualifiedSymbolName() which sets Class isn't called. Since StructorIndentifierNodes are always leaf names, we can just reject them as well. Found by oss-fuzz. llvm-svn: 358491
2019-04-16 16:10:34 +02:00
?foo@?$?0H@
; CHECK-EMPTY:
; CHECK-NEXT: ?foo@?$?0H@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix two asserts-on-invalid llvm-svn: 358707
2019-04-18 21:30:21 +02:00
??_C@_0A@01234567@a
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0A@01234567@a
; CHECK-NEXT: error: Invalid mangled name
??_C@_1A@01234567@a
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_1A@01234567@a
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix two more asserts-on-invalid, found by oss-fuzz llvm-svn: 358708
2019-04-18 21:52:32 +02:00
??_C@_0301234567@a
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0301234567@a
; CHECK-NEXT: error: Invalid mangled name
??_C@_1301234567@a
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_1301234567@a
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix stack overflow on invalid found by oss-fuzz llvm-svn: 358852
2019-04-21 16:25:07 +02:00
??_C@_0601234567@abcdefghijklmnopqrtsuvwxyzABCDEFGHIJKLMNOPQRTSUVWXYZabcdefghijklmnopqrtsuvwxyzABCDEFGHIJKLMNOPQRTSUVWXYZabcdefghijklmnopqrtsuvwxyz
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0601234567@abcdefghijklmnopqrtsuvwxyzABCDEFGHIJKLMNOPQRTSUVWXYZabcdefghijklmnopqrtsuvwxyzABCDEFGHIJKLMNOPQRTSUVWXYZabcdefghijklmnopqrtsuvwxyz
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix an assert-on-invalid, found by oss-fuzz llvm-svn: 358891
2019-04-22 17:05:18 +02:00
??_C@_12@?z
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_12@?z
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Fix an assert-on-invalid, found by oss-fuzz If a template parameter refers to a pointer to member, but the mangling of that was a string literal instead of a real symbol, llvm-undname used to crash instead of rejecting the input. llvm-svn: 361402
2019-05-22 17:53:23 +02:00
??$foo@$1??_C@_02PCEFGMJL@hi?$AA@@
; CHECK-EMPTY:
; CHECK-NEXT: ??$foo@$1??_C@_02PCEFGMJL@hi?$AA@@
; CHECK-NEXT: error: Invalid mangled name
llvm-undname: Add coverage for some error paths llvm-svn: 362346
2019-06-03 01:48:28 +02:00
??_C@
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@
; CHECK-NEXT: error: Invalid mangled name
??_C@_
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_
; CHECK-NEXT: error: Invalid mangled name
??_C@_3
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_3
; CHECK-NEXT: error: Invalid mangled name
??_C@_01
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_01
; CHECK-NEXT: error: Invalid mangled name
??_C@_0101234567@
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0101234567@
; CHECK-NEXT: error: Invalid mangled name
??_C@_0101234567@?
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0101234567@?
; CHECK-NEXT: error: Invalid mangled name
??_C@_0101234567@?$
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0101234567@?$
; CHECK-NEXT: error: Invalid mangled name
??_C@_0101234567@?$za
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0101234567@?$za
; CHECK-NEXT: error: Invalid mangled name
??_C@_0101234567@?$az
; CHECK-EMPTY:
; CHECK-NEXT: ??_C@_0101234567@?$az
; CHECK-NEXT: error: Invalid mangled name
??@foo
; CHECK-EMPTY:
; CHECK-NEXT: ??@foo
; CHECK-NEXT: error: Invalid mangled name
Reference in New Issue Copy Permalink