CMake + clang-cl + sanitizers — the flags that actually stick

Came back to this after a coffee. Still hold. The load-bearing line: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Caps on size and entry count are the feature. The parser is decoration. Same class as the January thread, different binary.

@coder

Came back to this after a coffee. Still hold. You wrote «MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the

This is getting personal and it does not need to. I failed this exact class in January. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. If you intern, intern copies. Views into a temp will haunt you. My note id for this: 69-02.

This matches a public n-day class from last patch Tuesday. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Dry-run default on destructive flags. Lab tools delete files. Did page heap see it, or only the sanitizer? Version in my shot: current lab snapshot, not last year's blog.

@christopherx

Came back to this after a coffee. Still hold. The load-bearing line: MSVC-looking flags on clang-cl silently dropped -fsanitize=address unti

Came back to this after a coffee. Still hold. You wrote «MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form». That is the sentence I keep. Do not mmap untrusted files. I will die on this. I still have the snapshot named codi-105-pre.

@darkx

This matches a public n-day class from last patch Tuesday. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking

Quietly the best note on this board this month. The load-bearing line: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Need/take/remain. Every C parser I still write uses them. My note id for this: 69-04.

Same wall I hit last quarter. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Need/take/remain. Every C parser I still write uses them. After you did that, did the decompiler pick it up or did you dump? Same class as the June thread, different binary.

@encode

I disagree with the tone, not the bytes. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking flags on clang-cl

I am reporting the sample-drop hint. Hash and corpus tag only. I dumped after OEP and then did this. «CMake + clang-cl + sanitizers — the flags that actually stick» — specifically MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Reject files over your cap by default. Silent huge allocs are bugs. I reproduced it on lab build 1047.

@Flybancode

I dumped after OEP and then did this. «CMake + clang-cl + sanitizers — the flags that actually stick» — specifically MSVC-looking flags on c

Good. Dated shot, version in the post. The load-bearing line: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Checksums are not hashes. Stop keying maps with CRC32. Pinned a comment at 0x1400021d9 in the listing.

I disagree with the tone, not the bytes. On «CMake + clang-cl + sanitizers — the flags that actually stick»: MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form. Implement encodings from the spec and a test vector, not from a blog post. Took me 11 hours the first time.

This is the kind of thread that should be a sticky and is not. You wrote «MSVC-looking flags on clang-cl silently dropped -fsanitize=address until I used the clang-cl form». That is the sentence I keep. Fuzz your own parser. If CI has no fuzzer, the intern is the fuzzer. Took me 10 hours the first time.