Unprocessed Trace exception logs memory address instead of error message

[HuntedFork]

Reproduce

Find a way to trigger this line

aws-xray-daemon/pkg/processor/batchprocessor.go

Line 106 in 4dce92e

log.Errorf("Unprocessed segment: %v", unprocessedSegment)

And observe an error message that looks like this

2025-11-07T22:49:42Z [Error] Unprocessed trace 1-690e7545-4f636120136ae307c2a705f4, segment: {0xc000016a50 0xc000016a60 0xc000016a70 {}}

As you can see instead of printing the error message, segmentId, and error code, it prints the memory address of those things.

I suspect this issue was introduced in the aws sdk 1->2 update because it doesnt exist in 3.3.15

[HuntedFork]

Easy ways to trigger this:

• Set the date of the segment to more then 7 days in the past
• Upload a really big segment
• Keep uploading segments to the same document until it breaks.

[bjrara]

Thanks for the context, will look into the fix. If you already have a patch, please feel free to submit a PR.