Nikolay Krasko
4087e650aa
Different bytecode can be generated for delegated property and for non-delegated one. Backend inspects DELEGATED_PROPERTY_CALL to understand the property type, and expects that this information had been already recorded into context. Frontend writes DELEGATED_PROPERTY_CALL into context during body resolve or type inference if type is not present. Either way in debugger context it may happen that the DELEGATED_PROPERTY_CALL won't be written into context. #KT-12678
9 lines
591 B
Plaintext
Vendored
9 lines
591 B
Plaintext
Vendored
LineBreakpoint created at delegatedPropertyInOtherFile.kt:9
|
|
!JDK_HOME!\bin\java -agentlib:jdwp=transport=dt_socket,address=!HOST_NAME!:!HOST_PORT!,suspend=y,server=n -Dfile.encoding=!FILE_ENCODING! -classpath !OUTPUT_PATH!;!KOTLIN_RUNTIME!;!CUSTOM_LIBRARY!;!RT_JAR! delegatedPropertyInOtherFile.DelegatedPropertyInOtherFileKt
|
|
Connected to the target VM, address: '!HOST_NAME!:PORT_NAME!', transport: 'socket'
|
|
delegatedPropertyInOtherFile.kt:9
|
|
Compile bytecode for t.a
|
|
Disconnected from the target VM, address: '!HOST_NAME!:PORT_NAME!', transport: 'socket'
|
|
|
|
Process finished with exit code 0
|