Darwin strip
is evil and can modify files even if they aren't valid Mach-O
#22520
Labels
0.kind: bug
Something is broken
I just spent some time tracking down a super weird bug because the standard
fixupPhase
was corrupting a .class file. Turns out that if you runstrip -S
incctools
against a .class file, it'll complain that it's not a valid Mach-O file but flip the endianness of the magic number at the start of the file anyway, thus making it an invalid Java class file.This will hurt us if we ever package things that contain raw class files not in jars.
Mostly leaving this as a reminder for myself to fix, but if someone else wants to look into it, please do!
The text was updated successfully, but these errors were encountered: