Journal, journal, was feeling bored on this day, and went hangout on www.hackerrank.com/ as usual. Today however, mono runtime replied to me and this is what it said:
* Assertion at mono-threads.c:448, condition `info' not met
Native stacktrace: mono() [0x49cf0c] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fd944fd9340] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7fd944c3acc9] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fd944c3e0d8] mono() [0x62a329] mono() [0x62a537] mono() [0x62a686] mono() [0x621728] mono() [0x5c7fed] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fd944fd9340] mono() [0x62a23e] mono() [0x62d7a1] mono() [0x611808] mono() [0x623ce0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7fd944fd1182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fd944cfe47d] Debug info from gdb: Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. No threads. ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. =================================================================
hmmm, dunno??, but seems like hackerrank may be using some session token to map a user to a running process. Does the stack affirms thread affinity ?? well don’t care about it at the moment.