Rrooach commented on issue #12855: URL: https://github.com/apache/nuttx/issues/12855#issuecomment-2283825359
@Gary-Hobson Hi, I am not quiet understand what is going on here, but after I pull the lastest mainline: 2ff2b82437, compile with:  and then I start the qemu: ```bash qemu-system-riscv64 -semihosting -M virt,aclint=on -cpu rv64 -smp 8 -bios none -kernel ./build_tt/nuttx -nographic -S -s ``` I still get a memory error: ```bash Thread 1 hit Breakpoint 2, exception_common () at /path/to/nuttx/arch/risc-v/src/common/riscv_exception_common.S:112 112 addi sp, sp, -XCPTCONTEXT_SIZE (gdb) bt #0 exception_common () at /path/to/nuttx/arch/risc-v/src/common/riscv_exception_common.S:112 #1 0x00000000800075dc in kasan_set_poison ( addr=addr@entry=0x80056dd0, size=<optimized out>, poisoned=poisoned@entry=false) at /path/to/nuttx/mm/kasan/kasan.c:188 #2 0x00000000800076ac in kasan_unpoison (addr=addr@entry=0x80056dd0, size=<optimized out>) at /path/to/nuttx/mm/kasan/kasan.c:241 #3 0x0000000080007d52 in mm_malloc (heap=heap@entry=0x80056b00, size=<optimized out>, size@entry=128) at /path/to/nuttx/mm/mm_heap/mm_malloc.c:325 #4 0x0000000080007d84 in mm_zalloc (heap=0x80056b00, size=size@entry=128) at /path/to/nuttx/mm/mm_heap/mm_zalloc.c:45 #5 0x00000000800078a8 in zalloc (size=128) at /path/to/nuttx/mm/umm_heap/umm_zalloc.c:70 #6 0x0000000080008ec8 in nx_start () at /path/to/nuttx/sched/init/nx_start.c:613 #7 0x00000000800005ee in qemu_rv_start (mhartid=<optimized out>, dtb=0x87e00000 "\320\r\376\355") at /path/to/nuttx/arch/risc-v/src/qemu-rv/qemu_rv_start.c:220 #8 0x0000000080000048 in _stext () at /path/to/nuttx/arch/risc-v/src/qemu-rv/qemu_rv_head.S:76 Backtrace stopped: frame did not save the PC ``` However, I can successfully run the nuttx if I disable "enable asan for the entire image" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
