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
If we add some global object like "std::vectorstd::string v = { "1", "2", "3" };" in our cpp file, which will be compiled later at runtime. Now we reload the project, everything is ok.
Then, our program exit normally(not by signal), it will be crashed with some message like:
*** Error in `./main': double free or corruption (fasttop): 0x00000000019aeac0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81329)[0x7ff37cb07329]
/root/jet-live_test/build/lib_reload1.so(_ZN9__gnu_cxx13new_allocatorISsE10deallocateEPSsm+0x20)[0xc269f0]
/root/jet-live_test/build/lib_reload1.so(_ZNSt16allocator_traitsISaISsEE10deallocateERS0_PSsm+0x2b)[0xc268db]
.....
The text was updated successfully, but these errors were encountered:
Sorry, somehow I missed your question, probably was too busy on my primary work.
It's important to note what compiler is used, I noticed that on some gcc versions there're weird issues happening here and there. I just checked this case on clang 18.1.8 on xubuntu 24.04, works fine
If we add some global object like "std::vectorstd::string v = { "1", "2", "3" };" in our cpp file, which will be compiled later at runtime. Now we reload the project, everything is ok.
Then, our program exit normally(not by signal), it will be crashed with some message like:
*** Error in `./main': double free or corruption (fasttop): 0x00000000019aeac0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81329)[0x7ff37cb07329]
/root/jet-live_test/build/lib_reload1.so(_ZN9__gnu_cxx13new_allocatorISsE10deallocateEPSsm+0x20)[0xc269f0]
/root/jet-live_test/build/lib_reload1.so(_ZNSt16allocator_traitsISaISsEE10deallocateERS0_PSsm+0x2b)[0xc268db]
.....
The text was updated successfully, but these errors were encountered: