Update JASM, removing setAggressivelyDropVars for a more sensible fix

meiMingle · Jan 11, 2025 · cf136f8 · cf136f8
1 parent 04affe1
commit cf136f8
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 4 deletions.
diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml
@@ -21,7 +21,7 @@ image-io-ext-ico = "3.0.2"
 instrument-server = "1.4.2"
 jackson = "2.17.1"
 jakarta-annotation = "3.0.0"
-jasm = "6e4ee7f22b"
+jasm = "1f1424fcba"
 jlinker = "1.0.7"
 jphantom = "1.4.4"
 junit = "5.11.0"

diff --git a/...core/src/main/java/software/coley/recaf/services/assembler/AbstractAssemblerPipeline.java b/...core/src/main/java/software/coley/recaf/services/assembler/AbstractAssemblerPipeline.java
@@ -47,9 +47,6 @@ public AbstractAssemblerPipeline(@Nonnull AssemblerPipelineGeneralConfig general
 	private void refreshContext() {
 		context = new PrintContext<>(generalConfig.getDisassemblyIndent().getValue());
 
-		// Enable aggressive variable name dropping to prevent use of bogus kotlin variable ranges.
-		context.setAggressivelyDropVars(true);
-
 		// Enable comments that outline where try-catch ranges begin/end.
 		if (pipelineConfig instanceof JvmAssemblerPipelineConfig jvmConfig && jvmConfig.emitTryRangeComments())
 			context.setDebugTryCatchRanges(true);