The program cannot tell you anything meaningful anymore, you are correct.
Resolving a null pointer is "undefined behaviour" per C/C++ programming standard. (As far as I am aware, any programming language with memory pointers defines it this way)
Anything past that operation has no meaning, as further operations (like calling a function or even simple addition) cannot be determinalistic anymore. An underlying core assumption was "proven wrong", but no result from such operations can be trusted.
I certainly would not believe a computer that claims it can divide by zero.
The operating system traps invalid instructions like these and immediately kills misbehaving programs like these. If left running for a while (to try to gather information about what exactly went wrong for example) the operating system itself is in jeopardy as it *has* to rely on the information the program provides.
Information that are, as established above, meaningless. Nobody would trust a calculator that "successfully" divides by zero.
So the only really good option the operating system has is to immediately kill the offending process and dump the content of the memory to disk for analysis (which is kind of what you can see in the picture).
Hannah /
npub1wa…06pd8
2024-08-18 03:22:40
in reply to nevent1q…e2x4
Author Public Key
npub1way0s9dacgmkyg4wzc3dmss0tmffqj75wqmrs78wf420v5f0z96qp06pd8Published at
2024-08-18 03:22:40Event JSON
{
"id": "9e9f82907dd83af515734ebec85ff4bbea8a34a1282f2e3857cd65da137133bf",
"pubkey": "7748f815bdc2376222ae1622ddc20f5ed2904bd470363878ee4d54f6512f1174",
"created_at": 1723951360,
"kind": 1,
"tags": [
[
"p",
"d1fa3c90b5976df354ab6128153fcd910fd28707a55e9b8dd15f61457558842a"
],
[
"e",
"a41cc854b6e1cd623aa56c0167102ecbf838831c0d3385a91b0980629be34ed3",
"",
"reply",
"040e7dabf271c1cd2c448e62be878e8755a8feb3d3baff89a9d28fc8e0a75f6a"
],
[
"e",
"199d63bec4b29e3fbbc8f9e94826191b72dd3ef4541990ed55b30dde07db0483",
"",
"root",
"d1fa3c90b5976df354ab6128153fcd910fd28707a55e9b8dd15f61457558842a"
],
[
"p",
"7748f815bdc2376222ae1622ddc20f5ed2904bd470363878ee4d54f6512f1174"
],
[
"p",
"040e7dabf271c1cd2c448e62be878e8755a8feb3d3baff89a9d28fc8e0a75f6a"
],
[
"proxy",
"https://moonserver.yorha.nexus/notes/9x2kfw61y4u8d2j5",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://moonserver.yorha.nexus/notes/9x2kfw61y4u8d2j5",
"pink.momostr"
],
[
"-"
]
],
"content": "The program cannot tell you anything meaningful anymore, you are correct.\nResolving a null pointer is \"undefined behaviour\" per C/C++ programming standard. (As far as I am aware, any programming language with memory pointers defines it this way)\nAnything past that operation has no meaning, as further operations (like calling a function or even simple addition) cannot be determinalistic anymore. An underlying core assumption was \"proven wrong\", but no result from such operations can be trusted.\nI certainly would not believe a computer that claims it can divide by zero.\n\nThe operating system traps invalid instructions like these and immediately kills misbehaving programs like these. If left running for a while (to try to gather information about what exactly went wrong for example) the operating system itself is in jeopardy as it *has* to rely on the information the program provides.\nInformation that are, as established above, meaningless. Nobody would trust a calculator that \"successfully\" divides by zero.\nSo the only really good option the operating system has is to immediately kill the offending process and dump the content of the memory to disk for analysis (which is kind of what you can see in the picture).",
"sig": "a89cc45f6e8478e42807d7e187419747d22366f8341bfc50b71e19f595f2651b6d620d0d49d349f592d4fc221242fa0f8be858ba37fe10cb734a40604f9d1a51"
}