diff options
| author | Pavel Labath <pavel@labath.sk> | 2018-09-09 06:01:12 +0000 |
|---|---|---|
| committer | Pavel Labath <pavel@labath.sk> | 2018-09-09 06:01:12 +0000 |
| commit | f8b825f689d6c84ae2d0f5e40697115053c734f2 (patch) | |
| tree | 2fb0c982ab3f22fb7b88596c3301109ea8cd192b /clang/unittests/Tooling/CompilationDatabaseTest.cpp | |
| parent | 9bd24527082ff753f43ef4e211013e3c5a0a459e (diff) | |
| download | llvm-f8b825f689d6c84ae2d0f5e40697115053c734f2.zip llvm-f8b825f689d6c84ae2d0f5e40697115053c734f2.tar.gz llvm-f8b825f689d6c84ae2d0f5e40697115053c734f2.tar.bz2 | |
Re-commit "Modernize NativeProcessProtocol::GetSoftwareBreakpointTrapOpcode"
This recommits r341487, which was reverted due to failing tests with
clang. It turned out I had incorrectly expected that the literal arrays
passed to ArrayRef constructor will have static (permanent) storage.
This was only the case with gcc, while clang was constructing them on
stack, leading to dangling pointers when the function returns.
The fix is to explicitly assign static storage duration to the opcode
arrays.
llvm-svn: 341758
Diffstat (limited to 'clang/unittests/Tooling/CompilationDatabaseTest.cpp')
0 files changed, 0 insertions, 0 deletions