Include start/end virtual addresses for extracted Go strings

[anushkasharmaa1]

This change updates ExtractMetadata.Strings to return objfile.GoString
instead of []string, allowing extracted Go strings to include their
start and end virtual addresses.

This builds on the existing -strings implementation and enables
downstream tooling (e.g. IDA / Binary Ninja plugins) to place string
literals at precise locations.

No behavioral changes when -strings is not used.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[stevemk14ebr]

Hi, please sign the CLA. We've removed the GoString structure in a recent PR. To continue this I'd like to a structure storing the start address of the string and the string contents, the end address can be calculated by the string length.

[anushkasharmaa1]

Thanks for the clarification! I’ll update the PR to use a structure containing the start address and the string contents instead of storing the end address.

…

On Thu, Mar 12, 2026 at 12:59 AM Stephen Eckels ***@***.***> wrote: *stevemk14ebr* left a comment (mandiant/GoReSym#84) <#84 (comment)> Hi, please sign the CLA. We've removed the GoString structure in a recent PR. To continue this I'd like to a structure storing the start address of the string and the string contents, the end address can be calculated by the string length. — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH7RHD5U3WSBMZ2YNKY5RAL4QG5ATAVCNFSM6AAAAACWEW6DMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANBRGYZTSNJSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>