rootvector2 opened a new pull request, #525: URL: https://github.com/apache/commons-bcel/pull/525
`LocalVariableInstruction.initFromFile` hardcodes length 4 for any `wide`-prefixed load or store, but `dump()` writes the `wide` prefix only when the index is above `Const.MAX_BYTE`. A `wide iload 5` is legal bytecode whose index fits in a byte, so it parses with `getLength()` 4 while `dump()` emits 2 bytes. I hit this auditing `wide` handling against `RET` and `IINC`, which persist the parsed flag and keep the two in sync. `InstructionList.setPositions` accumulates `getLength()`, so rebuilding a parsed method that carries one of these instructions shifts every following instruction 2 bytes and corrupts the branch offsets that span it. Deriving the parsed length from the same `wide()` test `dump()` already uses keeps length and emitted bytes in agreement, leaving the compact and non-wide paths untouched. - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project. - [ ] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI). - [ ] I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute? - [x] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself. - [x] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Each commit in the pull request should have a meaningful subject line and body. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
