If not, the GPL will not affect you. If so, does that not feel like mooching off the community?
Maybe his/her employer does not allow gpl software...
Then they aren't using GCC (or Linux) in the first place.
GPLv2 can be approved fairly easily. GPLv3 is a much tougher sell. For example, GCC is fine because there's really no alternative (or there wasn't before clang had full compatibility).
That's probably all not very applicable to gdb, but corporate policies might not allow such a nuanced perspective.
Also, reprogramming the ECU is already possible, and it's also not illegal to do it. It may very well void your warranty and it might be illegal to use the car on public roads after having reprogrammed the ECU, but neither of those two things are incompatible with the GPL.
Actually I think that would constitute a GPL violation on the part of the government (enforcing additional restrictions on the use of the software), although the government is generally not the one distributing the code (and also good luck holding them accountable even if they were).
> The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
> > that would constitute a GPL violation on the part of the government [if the government were the ones distributing it] [...]
It would be nice to close this loophole (prevent or at least disincentivise the goverment from making such laws), but it's not clear how that could be accomplished.
https://reviews.llvm.org/D75750
The feature itself is multi-platform and is not original to GDB.