Opened a FB already (FB20928652) but wanted to check here if anybody has seen similar or has better workarounds.
xcresulttool merge appears to crash immediately after launch in Xcode 26.1 (and in 26.2b1).
It does so regardless of any inputs passed in; the crash appears to be during argument parsing before any other logic is run, so it's not contingent on inputs.
Working example from 26.0.1 (passing in arbitrary strings for a minimum-reproducible-case, so we expect to see an error message) :
% /Applications/Xcode-26.0.1.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
Error: File or directory doesn't exist at path: b.
Usage: xcresulttool <subcommand>
See 'xcresulttool --help' for more information.
The same example crashes in 26.1:
/Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
zsh: trace trap /Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge
Again, this does crash in real use cases as well, the arbitrary strings are just for quick reproduction.
The stack trace appears to be during argument parsing (which from a quick look, did indeed change between 26.0.1 and 26.1). On 26.1+, garbage data seemingly gets passed to AbsolutePath.init.
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00000001002c6748 xcresulttool-26.1`normalize(absolute:)
frame #1: 0x00000001002c6438 xcresulttool-26.1`AbsolutePath.init(_:) + 28
frame #2: 0x000000010005a2c0 xcresulttool-26.1`Merge.run() + 372
frame #3: 0x000000010005b180 xcresulttool-26.1`protocol witness for ParsableCommand.run() in conformance Merge + 12
frame #4: 0x000000010011d3e4 xcresulttool-26.1`dispatch thunk of ReadableStream.close() + 16
frame #5: 0x000000010000148c xcresulttool-26.1`main + 156
frame #6: 0x00000001804d5d54 dyld`start + 7184
The only workaround we've found is to keep using 26.0.1's copy of xcresulttool, though that's obviously not ideal.
