My Haiku RISC-V port progress

Development OS
201

libgcc_s.so crashes here. More correct stack trace:

debug_server: Thread 559 entered the debugger: Debugger call: `abort() called'
stack trace, current PC 0xfffffff0ea291264  </boot/system/lib/libroot.so> _kern_debugger + 0x4:
  (0xfffffffb498fdf50)  0xfffffffac242ddec  </boot/system/lib/libgcc_s.so.1> uw_init_context_1 + 0x3ff
  (0xfffffffb498fe430)  0xfffffffac242e20a  </boot/system/lib/libgcc_s.so.1> _Unwind_RaiseException + 0x9b
  (0xfffffffb498fef00)  0xfffffff0ea306a28  </boot/system/lib/libroot.so> __cxa_throw + 0x41
  (0xfffffffb498fef30)  0xfffffff02c415bba  </boot/home/ExceptionTest> _Z5DoIntb + 0x4d
  (0xfffffffb498fef50)  0xfffffff02c415bf4  </boot/home/ExceptionTest> _Z2Dov + 0x21
  (0xfffffffb498fef80)  0xfffffff02c415c9e  </boot/home/ExceptionTest> main + 0x19
  (0xfffffffb498fefa0)  0xfffffff02c415b62  </boot/home/ExceptionTest> _start + 0x3f
  (0xfffffffb498fefd0)  0xfffffff0b1c436d4  </boot/system/runtime_loader> runtime_loader + 0xd5
  (0xfffffffb498ff000)  0x803a1af0

code returned by uw_frame_state_for() is _URC_END_OF_STACK, definitely wrong.

5 Likes