Alessandro Arzilli

I thought delve was always a static executable on linux.

I thought on macOS LD_PRELOAD was called something else (DYLD something?) > doesn't delve use cgo? Not on linux.

I didn't try implementing this because it would be affected by https://github.com/golang/go/issues/25841 at least. I also vaguely remembering some versions of go not producing any dwarf at all for macOS....

>It returns an error: Right, of course, because they aren't elfs. My bad. I guess the right one would be `otool -l` or something like that. Or `gobjdump -h ...`...

As you can see, no debug sections. Now that I think about it I knew this because I noticed when I changed the linker to make it able to emit...

I think it would behoove you to comment yourself on that thread, your first hand account of why you need it would be more persuasive than my second hand perception...

> e.g., I don't understand how you obtained the output that you cite, they look like they came from running readelf they are from `objdump --dwarf`, the GNU version, not...

It's probably because of dwarf compression, you probably have to disable it with `-ldflags='-compressdwarf=false'`

See https://github.com/go-delve/delve/blob/master/Documentation/internal/portnotes.md

Don't worry about DeepSource. See the document I linked above for things to worry about.