Consider this code:

import kotlinx.coroutines.experimental.delay
import kotlinx.coroutines.experimental.runBlocking

suspend fun subfunction() {
    println("One")
    delay(10)
    println("Two")
}

suspend fun someMethodTree() {
    subfunction()
}

suspend fun whatever() {
    someMethodTree()
}

fun main(args: Array<String>) {
    runBlocking {
        whatever()
    }
}

The stack trace at the "One" println would contain the methods leading up to it (whatever and someMethodTree), whereas at "Two", after the suspend on delay(), it would instead show the caller as "doResume", with the rest of the stack entries missing (instead it's all event loop internals and such)