You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the program highlighting the issue. For 2726 items in the CXX_VALUES vector, it causes a page fault. For 2725 items (one less) there is no page fault. This is happening both on the kvm and on the linuxu platforms.
A stack trace of the issue points to:
(gdb) bt
#0 std::__1::ios_base::Init::Init (this=<optimized out>) at /home/razvan/projects/unicore/unikraft-my/apps/t/build/libcxx/origin/libcxx-7.0.0.src/src/iostream.cpp:85
#1 0x0000000000204fae in __static_initialization_and_destruction_0 (__priority=65535, __initialize_p=1) at /home/razvan/projects/unicore/unikraft-my/apps/t/build/libcxx/origin/libcxx-7
.0.0.src/src/iostream.cpp:80
#2 _GLOBAL__sub_I__ZNSt3__13cinE () at /home/razvan/projects/unicore/unikraft-my/apps/t/build/libcxx/origin/libcxx-7.0.0.src/src/iostream.cpp:124
#3 0x000000000010c0b2 in main_thread_func (arg=0x3fdff50) at /home/razvan/projects/unicore/unikraft-my/unikraft.git/lib/ukboot/boot.c:135
#4 0x0000000000105757 in asm_thread_starter () at /home/razvan/projects/unicore/unikraft-my/unikraft.git/plat/common/x86/thread_start.S:39
#5 0x0000000000000000 in ?? ()
The highlighted instruction (=>) is the one where the issue occurs.
It seems to point to a C++ initialization issue in Unikraft, before the calling of the main() function.
It's possible to be related to memory alocation / initialization in the Unikraft startup sequence.
The text was updated successfully, but these errors were encountered:
This is the program highlighting the issue. For
2726
items in theCXX_VALUES
vector, it causes a page fault. For2725
items (one less) there is no page fault. This is happening both on thekvm
and on thelinuxu
platforms.A stack trace of the issue points to:
The highlighted instruction (
=>
) is the one where the issue occurs.It seems to point to a C++ initialization issue in Unikraft, before the calling of the
main()
function.It's possible to be related to memory alocation / initialization in the Unikraft startup sequence.
The text was updated successfully, but these errors were encountered: