Jeff Lockhart
07/04/2023, 3:30 AMJeff Lockhart
07/04/2023, 3:31 AM./gradlew clean :lib-module:linuxX64Test --tests package.TestClass.testName
This is the output:
...
> Task :lib-module:linuxX64Test FAILED
package.TestClass.testName[linuxX64] FAILED
Unknown
1 test completed, 1 failed
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':lib-module:linuxX64Test'.
> Test running process exited unexpectedly.
Current test: testName
Process output:
<standard output logs...>
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at <https://help.gradle.org>
BUILD FAILED in 22s
Jeff Lockhart
07/04/2023, 3:33 AMUnknown
with no stack trace, I'm able to narrow the line that fails with log statements. But I don't even get a POSIX signal, let alone an exception to indicate what went wrong.Jeff Lockhart
07/04/2023, 3:36 AM--stacktrace
, I just get this stack trace for where Gradle crashed, where I can see
Test running process exited unexpectedly.
Jeff Lockhart
07/04/2023, 3:37 AMkotlin.native.binary.sourceInfoType=libbacktrace
makes no difference. No stack trace either way.Jeff Lockhart
07/04/2023, 3:39 AMJeff Lockhart
07/04/2023, 3:43 AMactual
implementation code as Linux. It has also passed occasionally on Linux, but usually fails.Jeff Lockhart
07/04/2023, 3:46 AMJeff Lockhart
07/04/2023, 4:40 AMStableRef
right before removing a native C listener that used it in a staticCFunction
callback. Removing the listener before disposing it fixes the problem.
Oddly, after getting the underlying class reference with CPointer.asStableRef().get()
, I could log the non-null field references just fine (logging null
). It would crash with the Unknown
error if I tried to log the entire class reference or invoke the function, which one of the non-null fields holds.Jeff Lockhart
07/04/2023, 4:41 AMprintln()
log statements.napperley
09/05/2023, 11:52 PM