Lennart Poettering on Nostr: In many situations this new feature should be "good enough" to extract stack traces ...
In many situations this new feature should be "good enough" to extract stack traces from containers, but of course it's not going to be able to fully address the fact that containers and host typically are built with different compiler/debugging settings, i.e. that the coredump processing and the coredump paylad originate from different vendors with all the differences in generation this brings.
And of course, the security angle deserves attention: we are processing untrusted data…
Published at
2024-12-13 09:15:28Event JSON
{
"id": "985140ff7f971794d5eb8a0d20000f70994912870963dde190e32a65e4147c69",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1734081328,
"kind": 1,
"tags": [
[
"e",
"14ca6f91b405fd844c329b28df8b1849a3fb39a2a1e358557a4690f9a7452429",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/113644753957110187",
"activitypub"
]
],
"content": "In many situations this new feature should be \"good enough\" to extract stack traces from containers, but of course it's not going to be able to fully address the fact that containers and host typically are built with different compiler/debugging settings, i.e. that the coredump processing and the coredump paylad originate from different vendors with all the differences in generation this brings.\n\nAnd of course, the security angle deserves attention: we are processing untrusted data…",
"sig": "92bbfec8945fedf8c21a3210688d949e076832e9b5ed7054efc08ca253f6e29905000fb9759490252f2e649fb580b8ba4e9093de1250043028333cce967f5301"
}
