Visual C++ error reporting is a bit like using an LLM. If it hits a problem it tries to hallucinate a way to continue and then when it doesn't work out later you get bizarre error messages that have no obvious connection to the actual error.
If you read all of the error messages in sequential order you can find the point where it started hallucinating. But the error list in the GUI is (for reasons beyond my ability to understand) a cherry picked subset that often omits the start of the hallucinations.
Dan Piponi /
npub1xs…fgrae
2024-09-10 18:41:00
Author Public Key
npub1xs30e0pj7velktf5sxewnqf93tu2pdt3s6wtl6fug2tzgy8zxthsgfgraeSeen on
wss://relay.mostr.pubPublished at
2024-09-10 18:41:00Event JSON
{
"id": "46aefaa3f6fb6cabde281f0ddf8d7937debde26a51efbdc9c4910836ee251465",
"pubkey": "3422fcbc32f333fb2d3481b2e981258af8a0b571869cbfe93c42962410e232ef",
"created_at": 1725993660,
"kind": 1,
"tags": [
[
"proxy",
"https://mathstodon.xyz/users/dpiponi/statuses/113114720547061790",
"activitypub"
]
],
"content": "Visual C++ error reporting is a bit like using an LLM. If it hits a problem it tries to hallucinate a way to continue and then when it doesn't work out later you get bizarre error messages that have no obvious connection to the actual error.\n\nIf you read all of the error messages in sequential order you can find the point where it started hallucinating. But the error list in the GUI is (for reasons beyond my ability to understand) a cherry picked subset that often omits the start of the hallucinations.",
"sig": "8404aa395526174bd57b719b78cd65daa520ccff66255bc720a8cc9f0366d64216c46ffe282543950349521aa2254c1a61a0fc92b31741e39b45d67c22fe5b1e"
}