Context
Around a year and a half ago, I’ve asked my former company for some time to
work on an issue that was impacting the debugging capabilities in our project:
gdbserver couldn’t debug multithreaded applications running on a PowerPC32
architecture. The connection to the gdbserver was broken and it couldn’t
control the debug session anymore. Multiple people have already investigated
this problem and I had a good starting point, but we still weren’t sure in
which software component the issue lied: it could have been the toolchain, the
gdbserver, the Linux kernel or the custom patches we applied on top of the
kernel tree. We were quite far away from finding the root cause.
The maintainer also comes off as a colossal asshole about the whole thing who didn’t even deign to offer a scrap of credit to the programmer who found and fixed a six-year-old bug. If the article is truthful, the maintainer is the sort of toxic, power-tripping, self-obsessed repo czar that actively makes the open source community worse.
The maintainer also comes off as a colossal asshole about the whole thing who didn’t even deign to offer a scrap of credit to the programmer who found and fixed a six-year-old bug. If the article is truthful, the maintainer is the sort of toxic, power-tripping, self-obsessed repo czar that actively makes the open source community worse.