• @Strykker
    link
    1394 months ago

    Except the C++ “Core dumped” line is telling you it just wrote a file out with the full state of the program at the time of the crash, you can load it up and see where it crashed and then go and look at what every local variable was at the time of the crash.

    Pretty sure you can even step backwards in time with a good debugger to find out exactly how you got to the state you’re currently in.

            • ⸻ Ban DHMO 🇦🇺 ⸻
              link
              fedilink
              English
              114 months ago

              When you apply for a home loan or a passport:

              “Unfortunately we will have to reject your application”

              “Why?”

              “We have received several reports of failed sudo attempts and segmentation faults”

      • Elsie
        link
        fedilink
        224 months ago

        I believe it’s /var/lib/apport/coredump on Ubuntu.

        • @[email protected]
          link
          fedilink
          554 months ago

          imagine if it, like, told you this so you didn’t have to find out about it via a post on lemmy

              • @[email protected]
                link
                fedilink
                54 months ago

                I love gdb! I recently had to do a debug and wow its so cool! On gentoo I can compile everything with symbols and source and can do a complete stack trace.

              • @[email protected]
                link
                fedilink
                54 months ago

                …unless you build the executable with optimizations that remove the stack frame. Good luck debugging that sucker!

              • @[email protected]
                link
                fedilink
                24 months ago

                Am I the only one in this thread who uses VSCode + GDB together? The inspection panes and ability to breakpoint and hover over variables to drill down in them is just great, seems like everyone should set up their own c_cpp_properties.json && tasks.json files and give it a try.

          • @[email protected]
            link
            fedilink
            English
            -84 months ago

            Imagine if you knew the most basic foundational features of the language you were using.

            Next we’ll teach you about this neat thing called the compiler.

            • @[email protected]
              link
              fedilink
              English
              104 months ago

              I’m not a C/C++ dev, but isn’t apport Ubuntu’s crash reporter? Why would dumps be going into there?

              Though on a rhetorical thought, I am aware of systemd’s coredumptctl so perhaps its collecting dumps the same way systemd does.

              • @[email protected]
                link
                fedilink
                English
                11
                edit-2
                4 months ago

                https://wiki.ubuntu.com/Apport

                It intentionally acts as an intercept for such things, so that core dumps can be nicely packaged up and sent to maintainers in a GUI-friendly way so maintainers can get valuable debugging information even from non-tech-savvy users. If you’re running something on the terminal, it won’t be intercepted and the core dump will be put in the working directory of the binary, but if you executed it through the GUI it will.

                Assuming, of course, you turn crash interception on- it’s off by default since it might contain sensitive info. Apport itself is always on and running to handle Ubuntu errors, but the crash interception needs enabled.