{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifgmhznkdpj6bng4kajmtqt6tonvb4a33yyx7llf3wpuea7unghha",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mnn5ngkdkix2"
  },
  "path": "/viewtopic.php?t=33505&p=275304#p275304",
  "publishedAt": "2026-06-06T17:06:51.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://linux.die.net/man/5/core"
  ],
  "textContent": "> > /var/lib/systemd/coredump/\n>\n> I don't use systemd. Do you know where else it could be?\n\nHere are some options if you are using an init system such as sysvinit:\n\n- If kernel.core_pattern is set to a simple filename (e.g., core), the core dump may be saved in the current working directory of the crashed process.\n- If kernel.core_pattern specifies a path (e.g., /var/crash/core.%p), the dump should be saved to that specified location.\n\nYou may want to bring this topic up in the Devuan, MX, or antiX forums, where they could probably help pinpoint you based on your particular system setup.\n\nFor me on MX Linux using sysvinit, if I run the following command:\n\nCODE:\n\n\n    cat /proc/sys/kernel/core_pattern\n\nthe output I get is:\n\nCODE:\n\n\n    core\n\nwhich should mean that the core dump will be generated in the current working directory of the crashed process: https://linux.die.net/man/5/core\n\nBut, once again, asking for help in the Devuan, MX, or antiX forum would be more productive for you, as those forums will have experts in this area.\n\n* * *",
  "title": "General Discussion • Re: Do 'silent' crashes leave a report somewhere?",
  "updatedAt": "2026-06-06T17:06:51.000Z"
}