• @x00z
    link
    English
    361 day ago

    Just don’t write bugs LOL

  • Lucy :3
    link
    fedilink
    621 day ago

    Never have seen any .exe that logs anything. They’re literally black boxes.

      • @[email protected]
        link
        fedilink
        211 hours ago

        And it helpfully installs a scareware antivirus that changes your default search engine so you don’t have to go through the trouble!

  • boredsquirrel
    link
    fedilink
    271 day ago

    Tried to debug a flatpak

    downloads 6GB of devel stuff, tries to open a file in gdb, cries

    Finds out it is a kernel bug.

    Tries to get debug logs, even though that stuff is disabled “fOr sEcUrItY hArDeNinG”

    (Kernel 6.13 is a mess)

    • palordrolap
      link
      fedilink
      161 day ago

      .13

      Well there’s your problem.

      (Not 13 specifically. Just the odd numbered sub-version in general. But 13 if you’re superstitious, I guess.)

  • @rImITywR
    link
    English
    381 day ago

    Debugging requires hard liquor.

    • @[email protected]
      link
      fedilink
      English
      131 day ago

      I’ve found that 3 beers over an hour period is my sweet spot for debugging. But I would definitely need liquor to debug wine.

      • Ignotum
        link
        211 hours ago

        If I had to pick bugs out of my wine I would probably also switch to drinking liquor instead

    • @ikidd
      link
      English
      11 day ago

      Way ahead of you.

  • Ekky
    link
    fedilink
    91 day ago

    “Is this ‘Critical Error’ the reason for the crash, or just another ill-labeled exception?”

    I love WINE and it’s forks, but man, how can any program produce so many errors during optimal operation? (A rhetorical question, as I believe we all know the tragicomedic reason being Microsoft)

  • @devfuuu
    link
    41 day ago

    I’m more of a beer person myself.