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

    Thank you for explaining. This helps me understand both his and this here situation.

    First of all, I‘m totally ok with it being absurd. It was my impression that this person has been wronged and should be appropriately compensated for their (shit ton of) work. From the text, it seemed like there is a way to get this compensation (in the form of recognition of some sort).

    I‘m totally fine with being told that he misrepresented the situation and he‘s more going off a principle here which would never be enforceable. If there were such a „standard“ for recognition for kernel controbution, one could definitely try to enforce it.

    In general, I have no problem with standing corrected. What I do have a problem with is the way people in IT centric communities on lemmy (and reddit) behave in general.

    Obviously you were kind enough to explain instead and without being violent or abusive. I highly respect that. Thanks again.