Timings were interesting today. I only measured pa...

# advent-of-code

[Joris PZ]

Timings were interesting today. I only measured part 2, (first/best) out of 25: JVM 911/563 ms, JS 7972/5725 ms. Native did not finish but exited very quickly with

Process finished with exit code -1,073,741,571.

Anyone have any idea how I can find out what went wrong there? My native debugging skills are less than weak

[Joris PZ]

I think this is exit code 0xC00000FD, which seems to be a stack overflow?

[karelpeeters]

That's a segfault IIRC.

[Joris PZ]

Interesting, thanks for testing! Slow has been true for all days, alas.

What OS and shell are you running this from? And did you do anything interesting to compile?

[karelpeeters]

PHP seems to have a similar issue: https://www.reddit.com/r/adventofcode/comments/a4kvmv/day_9_segfaulting_in_php_for_part_2

[SiebelsTim]

I'm on Ubuntu 18.04.1 and compiled using gradle which uses the kotlin-multiplatform plugin version 1.3.11

[SiebelsTim]

Segfaults using konan though: info: kotlinc-native 1.3.0-rc-116 (JRE 1.8.0_101-b13)
Kotlin/Native: 0.9.3

It recurses infinitely in void (anonymous namespace)::ScanBlack<true>(ContainerHeader*) ()

e: The gradle one uses:
info: kotlinc-native 1.3.11 (JRE 1.8.0_101-b13)
Kotlin/Native: 1.0.3


What versions do you use?

[Joris PZ]

Windows 10, multi-platform plugin 1.3.10

[Joris PZ]

I'll see what happens when I upgrade to 1.3.11

[Joris PZ]

Huh! After upgrading, it manages to calculate the proper result once, then again exits again with 0xC00000FD. So it got a bit further but it is still draining the stack