Alessandro Arzilli

Closing this, at this point doing extra stuff after startup would be too much of a backwards incompatible change.

Doesn't look like there's been enough interest for this in the past 3 years.

Closing, fixed by 7151c6c

> What's really suspicious is the extremely long wait times reported (52 years?) Delve bug, please disregard.

> (...) McAfee (...) asyncpreemption See also #42528. I wonder if these anti viruses aren't doing debugger-like things and running into some variant of #36494.

Some changes need to happen to go, then delve will be updated to match. If all goes according to plan it will happen in time for 1.21 in july.

Delve's side of this needs to be implemented. At the moment I don't have access to a working VM (and none of the builders have a version of macos that...

@rstcruzo presumably it's coming from loadBinaryInfoMacho, you should check that it can actually load the plugin binary. Could be something in go's standard library.

I checked out the latest version of macOS (13.4) and it still has a bugged version of dsymutil.

No, build something and check that the debug_frame section is correct (you could probably find out from the version of llvm but I don't know which version has the fix).