is there any way to get a more... usable stacktrace other than `Throwable().printStackTrace()` as im...

# announcements

[Smallville7123]

is there any way to get a more... usable stacktrace other than Throwable().printStackTrace() as im trying to find what line in the function my function is throwing from

[tddmonkey]

This information is in the stack trace

[Smallville7123]

how would i aquire it?

[tddmonkey]

What do you mean? What’s your context?

[Smallville7123]

for example

fun abort(e: String = "Aborted"): Nothing {
    println("Aborting with error: $e")
    println("stack trace:")
    Throwable().printStackTrace()
    throw Exception(e)
}

fun main() {
    a()
}

fun a() {
    println("aborting from a:2 from SampleLinux.kt:20")
    abort()
}

output:

aborting from a:2 from SampleLinux.kt:20
Aborting with error: Aborted
stack trace:
kotlin.Throwable
        at kfun:sample.abort$default(kotlin.String;kotlin.Int)kotlin.Nothing (0x21a208)
        at Konan_start (0x21a182)
        at Konan_run_start (0x21a0f3)
        at Konan_main (0x21a047)
        at __libc_start_main (0x7f305064c223)
        at  (0x210029)
        at  ((nil))
Uncaught Kotlin exception: kotlin.Exception: Aborted
        at kfun:sample.abort(kotlin.String)kotlin.Nothing (0x21a490)
        at kfun:sample.abort$default(kotlin.String;kotlin.Int)kotlin.Nothing (0x21a208)
        at Konan_start (0x21a182)
        at Konan_run_start (0x21a0f3)
        at Konan_main (0x21a047)
        at __libc_start_main (0x7f305064c223)
        at  (0x210029)
        at  ((nil))

[tddmonkey]

Is that kotlin native?

[Smallville7123]

yes

[tddmonkey]

you should probably ask that in the #C3SGXARS6 channel then

[Smallville7123]

ok

[Mike]

Comment on code if you’re worried about performance.

You’re creating the stacktrace twice in your existing code because you create a Throwable, and an Exception.

val e = Exception(message)
e.printStackTrace()
throw e

or

throw Exception(message).also {
   it.printStackTrace()
}

[Smallville7123]

ok? and im only interested in obtaining a backtrace

[Mike]

Just an unasked for code review/comment. Creating a stacktrace can be expensive, and your original code was creating it twice. That’s all my point was.

Don’t know of a cleaner approach to creating it, so nothing useful specific to your question.

[tddmonkey]

Are you only interested in generating a stack trace, or do you want to throw it too? Your code indicates you also want to throw it. If you just want the stack trace you could do it directly:

`Thread.currentThread().stackTrace

[Smallville7123]

is a backtrace and a stacktrace the same thing?

[Smallville7123]

@tddmonkey Unresolved reference: Thread