IssueTracker

Versions

• r8 version: R8 main (build engineering)
• art version: ART version 2.1.0 x86_64
• java version: 17.0.10

Description

When processing jar files to generate dex files using D8 and R8 respectively, the resulting dex files behave inconsistently during execution. The dex file generated by R8 crashes upon execution with the error "Exception in thread 'main' java.lang.NullPointerException," which should actually be caught. In contrast, the dex file generated by D8 executes normally. We suspect this is an issue with R8.

Step to Reproduce

1. javac -source 8 -target 8 -cp . Test.java
2. jar cvf classes.jar ./*.class
3. java -cp r8.jar com.android.tools.r8.R8 --pg-conf rules.pro --release --output ./ ./classes.jar
4. env ANDROID_LOG_TAGS=*:f ANDROID_DATA=./ /path/to/art --64 --no-compile -cp ./classes.dex Test > result

Expected Result(d8 dex output)

over

Actual Result(r8 dex output)

Exception in thread "main" java.lang.NullPointerException
	at Test.main(SourceFile:11)

Testcase Source Code

import java.net.SocketAddress;
import java.nio.ByteBuffer;
import java.nio.channels.DatagramChannel;
class Test {
  void a(String[] b) {
    ByteBuffer byteBuffer= null;
    SocketAddress socketAddress = null;
    DatagramChannel datagramChannel = null;
    try {
      if (socketAddress == null)
        datagramChannel.receive(byteBuffer);
    } catch (Throwable $) {
    }
  }
  public static void main(String[] c) {
    Test e = new Test();
    e.a(c);
    System.out.println("over");
  }
}

rules.pro

-injars classes.jar
-libraryjars android.jar
-keep class Test { public main(java.lang.String[]); }