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.
  • @kairosOPEnglish
    -1•9 months ago

    The way that you jumped straight onto broadcasting drama

    I’m not broadcasting drama, I’m sharing my side of the story on my personal blog and distribute it to other social media platforms.

    your very first Linux kernel patch stumbled on the code review stage

    The patch didn’t stumble on the code review stage, the PowerPC maintainer didn’t want to accept patches from me and implemented his own fix.

    I would hate to work with you because I would feel that I would be risking being subjected to a very public character attack each time I had to review one of your patches.

    Why would you hate people who would describe their interactions with you? The only reason I see is that you would hate how you’ve dealt with them.

    • @[email protected]English
      12•9 months ago

      I’m not broadcasting drama, I’m sharing my side of the story on my personal blog and distribute it to other social media platforms.

      That’s literally broadcasting drama.