Alessandro Arzilli
Alessandro Arzilli
> is it ok to simply concatenate buildFlags setting with ' '? With a space? No it will not work if they contain spaces themselves. They need to be quoted...
> or just call SplitQuotedFields on each. This would actually be wrong, BTW. But something like it that strips quotes. OTOH I think doing nothing and letting > ``` >...
No, it's fine. I was just pointing out that: > Historically, the subtle difference between how dlv is parsing the build flags and how go command is parsing the flags...
Sorry for the confusion.
I think this was implemented by 7151c6cbcc555c8d15a7f959adc37565d9aed6f2
`p os.Args` will do this
os.Args needs to be initialized by the go runtime so it won't be available immediately after starting a program. Also, as you note, you can't read it after the program...
See [Delve's porting guide](https://github.com/go-delve/delve/blob/master/Documentation/internal/portnotes.md). Also see the build failures.
In general this seems mostly fine. The main two problems are that (a) it doesn't compile on anything but go1.18 and (b) we need to do CI for it.
> We can provide machines with loongarch64 instruction architecture that can be accessed remotely. Of course, we can also provide physical machines for CI. What resources do we need to...