> With Cosmopolitan Libc, you can have gdb integration and detailed backtraces for your C program in just one line: add ShowCrashReports(); at the start of the main function
> Now if you have gdb available on $PATH, you would get a TUI (terminal user interace) showing the register contents and the backtrace of the crash
doesn't the first paragraph clearly establish that?
I mean it says these are part of Cosmopolitan but these just seem like standard tools that I don't need to use Cosmopolitan for…
There are some things from Cosmopolitan that demonstrate its integration with GDB and other standard tools. For example, the article demos ShowCrashReports() which is nicely integrated with GDB. Also --ftrace, not to be confused with the kernel feature of the same name.
It explains how to use them in the way cosmopolitan provides them, which is clearly different from how other environments do it, even though they of course have ways of getting the same kind of information.
There are many wonderful tools that help understand what our code is doing (compiler explorer, gdb, valgrind, ftrace, perf record, strace, ASAN/UBSAN). I wrote this blog post because using the debugging tools with Cosmopolitan Libc helped me learn and improve at programming. If you have other resources that can help me understand more about how my code works, I am happy to learn.