godebug build not using generated package files

Nobody has claimed this yet.

Greetings, thank you for creating such an awesome tool for go developers. I have tried to use godebug to debug my project with many packages, I use following command to build:

godebug.exe build -instrument=github.com/..../cms/data

And then run the built binary but no breakpoint is activated.

Then I use -godebugwork to get generated go files, copy all the generated package files to origin directory, and use normal go build/run, I can then successfully enter the breakpoint and print vars etc...

I wonder why godebug build didn't use its generated files to build the executable, whether it's a bug or what did I do wong?

Thank you!

Start by reproducing the reported `godebug.exe build -instrument=...` behavior and compare it with a normal Go build after using `-godebugwork` and copying the generated package files. Trace how the build command consumes generated files; done means the instrumented executable activates breakpoints and permits variable inspection without manual copying.

Written by the indexing model from the issue text.