Add o6/f test case and fix method annotation ordering in Smali parser

[Copilot]

Adds the o6/f class test case for bafybeiebe27ylo53trgitu6fqfbmba43c4ivxj3nt4kumsilkucpbdxtqq DEX file to the parseDexAgainstSmaliMacro test suite.

Changes

• Added test case: { smaliFilePath: 'o6/f', isolate: true } to the test array for the target DEX file

• Fixed method annotation sorting in Smali parser: The existing lexicographic sort was using localeCompare() which is locale-aware and incorrectly orders method names (e.g., treating 'H' > 'd' in some locales). Changed to use direct code point comparison (< operator) to match the DEX file format specification, which uses byte-by-byte comparison for sorting method IDs in the method_id table.

The o6/f class test revealed this bug - the Smali parser was producing method annotations in order 'd, H, p' (due to locale-aware sorting) while the DEX file correctly had them as 'H, d, p' (code point order where 'H'=72 < 'd'=100).

• Fixes Add bafybeiebe27ylo53trgitu6fqfbmba43c4ivxj3nt4kumsilkucpbdxtqq + o6/f parseDexAgainstSmaliMacro test like others and make it pass #191

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add bafybeiebe27ylo53trgitu6fqfbmba43c4ivxj3nt4kumsilkucpbdxtqq + o6/f parseDexAgainstSmaliMacro test like others and make it pass</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add bafybeiebe27ylo53trgitu6fqfbmba43c4ivxj3nt4kumsilkucpbdxtqq + o6/f parseDexAgainstSmaliMacro test like others and make it pass #191

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[futpib]

@copilot remove sortMethodAnnotations, this is almost as bad as just skipping the test. Check if smali code has the correct order of method annotations, check that dex file has the correct order of method annotations, check if our smali parser has the same order of annotations, check if our dex parser has the correct order of annotations, fix whichever parser is wrong or both

[coveralls]

Pull Request Test Coverage Report for Build 19380680309

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.03%) to 94.101%

---

Totals
Change from base Build 19379304572:	0.03%
Covered Lines:	7976
Relevant Lines:	8469

---

💛 - Coveralls

[Copilot]

@copilot remove sortMethodAnnotations, this is almost as bad as just skipping the test. Check if smali code has the correct order of method annotations, check that dex file has the correct order of me...

Fixed in commit 810f635. The root cause was that the existing lexicographic sort was using localeCompare() which is locale-aware - in some locales it treats uppercase letters as coming after lowercase (e.g., 'd' < 'H'). However, the DEX file format sorts method IDs using byte-by-byte (code point) comparison where 'H' (72) < 'd' (100).

Changed the sort to use direct < comparison instead of localeCompare(), which matches the DEX specification. Both the o6/f test (which revealed the bug) and the m/g test now pass.