JcStateResolver crashed with Unexpected ref

Open
#162 0 comments 0 reactions 1 assignee View on GitHub

@Damtev is already working on this.

Since Nov 28, 2023.

Assessment

This issue has not been assessed yet.

Description

bug

Run ContestEstimator with the following options:

timeLimit = 30
methodFilter = "com.google.common.base.internal.Finalizer.*"
projectFilter = listOf("guava-26.0")

The following problem is found in logs:

java.lang.IllegalArgumentException: Unexpected ref: (id:8)java.lang.Class#getName0():#0
	at org.usvm.model.ModelKt.modelEnsureConcreteInputRef(Model.kt:97) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.collection.field.UFieldsModelRegion.read(UFieldsModelRegion.kt:19) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.collection.field.UFieldsModelRegion.read(UFieldsModelRegion.kt:13) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.memory.UReadOnlyMemory$DefaultImpls.read(Memory.kt:70) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.memory.UReadOnlyMemory$DefaultImpls.read(Memory.kt:73) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.memory.UWritableMemory$DefaultImpls.read(Memory.kt:82) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.model.UModelBase.read(Model.kt:35) ~[usvm-core-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveLValue(JcTestStateResolver.kt:93) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.allocateAndInitializeObject(JcTestStateResolver.kt:266) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveObject(JcTestStateResolver.kt:223) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:153) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:111) ~[main/:?]
	at org.usvm.api.util.JcTestStateResolver.resolveReference(JcTestStateResolver.kt:171) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveExpr(JcTestStateResolver.kt:101) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:177) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:111) ~[main/:?]
	at org.usvm.api.util.JcTestStateResolver.resolveReference(JcTestStateResolver.kt:171) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveExpr(JcTestStateResolver.kt:101) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveLValue(JcTestStateResolver.kt:95) ~[usvm-jvm-comp-231128-22.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.createUTest(JcTestExecutor.kt:133) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor.execute(JcTestExecutor.kt:70) ~[main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:177) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:170) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:277) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:271) [main/:?]
	at org.usvm.statistics.collectors.CoveredNewStatesCollector.onStateTerminated(CoveredNewStatesCollector.kt:26) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.statistics.CompositeUMachineObserver.onStateTerminated(UMachineObserver.kt:48) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.UMachine.run(Machine.kt:66) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.machine.JcMachine.analyze(JcMachine.kt:195) [usvm-jvm-comp-231128-22.jar:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:269) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:267) [main/:?]
Dominant language
Kotlin
Stars
33
Forks
27
Avg merge
4d 3h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UnitTestBot/usvm

All issues in UnitTestBot/usvm

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.