org.ibex.nestedvm.Runtime$ReadFaultException: fault at: 0x0 at 0x6d0dc: ??:0 In your example, 0x0 is the memory location being addressed by your mips program and 0x6d0dc is the instruction pointer of the mips program at the time. Once you've recompiled your C code with -g -O0 and you run the code using the nestedvm interpreter, you can retrieve the crashing line of C code by: mips-unknown-elf-addr2line.exe -e your_program.mips 0x6d0dc Unfortunately, you won't get a C stack backtrace.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Unknown author, 1 year ago
fault at: 0x0 at 0x6d0dc: ??:0 In your example, 0x0 is the memory location being addressed by your mips program and 0x6d0dc is the instruction pointer of the mips program at the time. Once you've recompiled your C code with -g -O0 and you run the
org.ibex.nestedvm.Runtime$ReadFaultException: fault at: 0x0 at 0x6d0dc: ??:0 In your example, 0x0 is the memory location being addressed by your mips program and 0x6d0dc is the instruction pointer of the mips program at the time. Once you've recompiled your C code with -g -O0 and you run the code using the nestedvm interpreter, you can retrieve the crashing line of C code by: mips-unknown-elf-addr2line.exe -e your_program.mips 0x6d0dc Unfortunately, you won't get a C stack backtrace.
at org.ibex.nestedvm.Runtime.unsafeMemRead(Runtime.java:413)
at org.ibex.nestedvm.Runtime.memRead(Runtime.java:401)
at org.ibex.nestedvm.Interpreter.runSome(Interpreter.java:502)
at org.ibex.nestedvm.Interpreter._execute(Interpreter.java:51)
at org.ibex.nestedvm.Runtime.__execute(Runtime.java:506)
at org.ibex.nestedvm.Runtime.execute(Runtime.java:523)
at org.ibex.nestedvm.Runtime.run(Runtime.java:545)
at org.ibex.nestedvm.Runtime.run(Runtime.java:538)
at org.ibex.nestedvm.Interpreter.main(Interpreter.java:783)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.