About GDB Debugging the Go Language program appears in the OS. Problems with args not printing

This is a creation in Article, where the information may have evolved or changed.

About GDB Debugging the Go Language program appears in the OS. Problems with args not printing

In fact, the problem to the current position is almost no solution. (So far, no gdb has been put in)

http://comments.gmane.org/gmane.comp.lang.go.general/117243

is indeed able to pass ' OS. Args ' Way to print

And at the same time, GDB, for C + + and go, their print method is actually different.

Pro-Test, in C, when debugging with GDB can be used to turn a strong address after the use of the string to print. But the same approach doesn't work in go.

This is simply sad ... I toss it for half a day, or no fruit. The go language is still relatively new. It often means that it is imperfect. There is no well-equipped debugging tool. GDB's support for Go is certainly not good for C, so many years of accumulation are there.

Suddenly there is a feeling, thinking about programming language. What exactly is the programming language called a good language?

It is foolish to think that not only is the syntax clear enough, the assembler code generated by the language compiler is sufficiently streamlined and must have a powerful debugging tool.

C has been so widely circulated that it has been such a dick for decades. The audience is not just the big cows that don't need to be debugged, there's a whole bunch of programming beginners, anyway, programming is going to make mistakes. For ordinary people, there are bugs to be debugger.

Also have to sigh, decades ago those giants are too bull, no gdb, GitHub, Google, the program is also transferred out, but for a want to be widely circulated, become an important tool of social programming language, missing a perfect debugger, it means that the language of failure.

Oh, humble opinion, pull a light just ... Beginner Go