Mads Ager
7d7b9262e7
These line number tests only tested that a set of line numbers where present in the java bytecode. Not that they would be hit in the right order by the debugger. Moving them to stepping tests fixes that. This exposes a couple of issues (in particular around try-catch-finally) that should be fixed. A number of tests are marked as failing now. Will investigate and work on fixes next.
33 lines
661 B
Kotlin
Vendored
33 lines
661 B
Kotlin
Vendored
// FILE: test.kt
|
|
|
|
fun box() {
|
|
foo()
|
|
bar()
|
|
}
|
|
|
|
fun foo(i: Int = 1) {
|
|
}
|
|
|
|
inline fun bar(i: Int = 1) {
|
|
}
|
|
|
|
// TODO: The JVM_IR backend has line number 11 for the inlined
|
|
// default argument handling both before and after the actual
|
|
// body of bar. That is consistent with what happens with the
|
|
// $default method in the non-inlined case, but it is not what
|
|
// happens with the JVM backend.
|
|
|
|
// FORCE_STEP_INTO
|
|
// LINENUMBERS
|
|
// test.kt:4 box
|
|
// test.kt:8 foo$default (synthetic)
|
|
// test.kt:9 foo
|
|
// test.kt:8 foo$default (synthetic)
|
|
// test.kt:5 box
|
|
// test.kt:11 box
|
|
// test.kt:12 box
|
|
// LINENUMBERS JVM_IR
|
|
// test.kt:11 box
|
|
// LINENUMBERS
|
|
// test.kt:6 box
|