0

I am running one application on linux with valgrind on my custom hardware ARM architecture board, which access external DDR memory (not present on board) causing application to crash with following reason

Bad mode in Error handler detected on CPU3. code 0xbf000002 -- SError Kernel Panic- not synching bad mode

I dont see this problem when application tries to access on board local DDR memory.I dont see same problem with other memory leak tools like dmalloc or address sanitizer. is this there any known problem and solution for this issue ?

not sure if I have given complete info let me know if you need more details.

Thanks in advance for you time & effort.

I was using valgrind memcheck tool to report memory leak issues from my application.

Sanket Jadhav
  • 1
  • From the OS perspective, is there any difference between local and external memory? – Paul Floyd Dec 02 '22 at 11:13
  • I don't think so, Address ranges only differs for both memories. For external memory we have controller in between (controller is simple in functionality), no sure could that cause anything (cannot overrule) but not having problem with other mem leak tools – Sanket Jadhav Dec 05 '22 at 05:36
  • I think your best hope is to log a bug on the kde bugzilla with a log containing verbose (-v -v -v -v) and debug (-d -d -d -d) and syscalls (--trace-syscalls=yes). – Paul Floyd Dec 06 '22 at 10:53
  • Ok Paul. I will collect logs and check on kde bugZilla – Sanket Jadhav Dec 14 '22 at 11:47

0 Answers0