3 ms·
What fails? Some commercial C/C++ compiler producers invest into a debugger typically because some of their customers use it on a platform without a good built-
by tagrun 8y ago
What fails? Some commercial C/C++ compiler producers invest into a debugger typically because some of their customers use it on a platform without a good built-in debugger. Yes, some systems had debuggers. The point is, some didn't.
I said compiled language, which Python isn't. Yes, gdb won't help you debugging scripting/VM languages.
Anyway, this is getting off topic, as we're talking about the alleged lack for debuggers for Go binaries for today's Go users, and neither of the things you mentioned are relevant. In my experience, nitpicking rarely leads to anything fruitful.
- pjmlp 8y agoThose some commercial producers as you put it, have invested in debuggers for BASIC, Pascal, Modula-2, PL/S, PL/8, NEWP, C, C++ and Ada for IBM/360, VAX/VMS, IBM 400, Solaris, Aix, HP-UX, Tru64, Irix, by IBM, Unisys, DEC, Compaq, SGI and HP themselves. And if I have to mention a FOSS compiled language instead of Python, with debugger support out of the box, then Oberon, Modula-2, FreeBasic, Gambas and FreePascal come to mind.