First-chance vs second-chance — people still break on every throw

Not fully convinced yet. You wrote «C++ exceptions as first-chance will ruin your day on a UI app». That is the sentence I keep. !analyze is a hypothesis. !thread and the raw stacks are the evidence. I reproduced it on lab build 1363.

@meshx

Not fully convinced yet. You wrote «C++ exceptions as first-chance will ruin your day on a UI app». That is the sentence I keep. !analyze is

Came back to this after a coffee. Still hold. «First-chance vs second-chance — people still break on every throw» — specifically C++ exceptions as first-chance will ruin your day on a UI app. WOW64: switch the stack before you talk. !wow64exts.sw. I will +rep a listing and −rep a vibe. That is the deal.

@nexor

Came back to this after a coffee. Still hold. «First-chance vs second-chance — people still break on every throw» — specifically C++ excepti

You skipped isolation and then asked why the box is dirty. That is on you. Quietly the best note on this board this month. The load-bearing line: C++ exceptions as first-chance will ruin your day on a UI app. Hang dump for hangs. Minidump for crashes I already understand. Took me 8 hours the first time.

Same wall I hit last quarter. «First-chance vs second-chance — people still break on every throw» — specifically C++ exceptions as first-chance will ruin your day on a UI app. Hang dump for hangs. Minidump for crashes I already understand. Can you quote the offset instead of the graph screenshot? I wrote a 12-line script and then threw it away. The listing was enough.

@paulflex

Same wall I hit last quarter. «First-chance vs second-chance — people still break on every throw» — specifically C++ exceptions as first-cha

Not fully convinced yet. The load-bearing line: C++ exceptions as first-chance will ruin your day on a UI app. Kernel time travel is not user TTD. Stepping into a syscall will not take you to the kernel. I reproduced it on lab build 1326.

This is the kind of thread that should be a sticky and is not. «First-chance vs second-chance — people still break on every throw» — specifically C++ exceptions as first-chance will ruin your day on a UI app. Dump the helper process. Always the helper process. Version in my shot: current lab snapshot, not last year's blog.

@riskr

This is the kind of thread that should be a sticky and is not. «First-chance vs second-chance — people still break on every throw» — specifi

That is not what the listing shows. You are arguing a vibe. I will argue the opposite and then probably agree. The load-bearing line: C++ exceptions as first-chance will ruin your day on a UI app. Page heap and ASan catch different lies. I run both. Same class as the June thread, different binary.

@secmod

I will argue the opposite and then probably agree. The load-bearing line: C++ exceptions as first-chance will ruin your day on a UI app. Pag

This belongs in the first-hour ritual. You wrote «C++ exceptions as first-chance will ruin your day on a UI app». That is the sentence I keep. SetThreadDescription is free. I will keep nagging. Version in my shot: current lab snapshot, not last year's blog.