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.
  • 1rre@discuss.tchncs.de
    10·
    1 year ago

    There’s a difference between being a team player and a subservient pawn though - if the maintainer wanted to play as a team they would’ve suggested changes to the patch and accepted OP’s PR. As it happens they didn’t as they clearly have some sort of a power/superiority complex or something, or at best are dismissive of others to the detriment of the project they work on