Emulator

Can you try enabling the MMU on the game properties page?

yes, i tried to set every option to value that equaling compatible one by one at a time but it didn't work

I need a Dolphin stack trace to do anything here; what needs to be done here probably depends on which GetPointer() call is causing this.

how can i try to report neccessary infos you need? May i use internal dolphin debugger and logger or ubuntu built-in debugger?
i tried backtrace using gdb in ubuntu but met 'segmentation fault'. Latter i tried Valgrind but met warning of something sort of '... #undef map_32bit'

gdb should work. You probably need to tell it to ignore segfaults; something like "handle SIGSEGV noprint pass". See http://www.sourceware.org/gdb/onlinedocs/gdb/Signals.html .

i have used gdb to backtrace and reported in the following link http://pastie.org/10073964
the report generated in the below sequence:
-> gdb /usr/games/dolphin-emu 2>&1 | tee ~/gdb-dolphin-emu.txt
-> (gdb) handle SIGSEGV pass noprint
-> (gdb) run

The program would start. Performed any actions necessary to reproduce the warning. When the program hung but didn't crash i pressed ctrl+c in gdb. While the program was frozen and then continued with the next step
-> (gdb) backtrace full
-> (gdb) info registers
-> (gdb) x/16i $pc
-> (gdb) thread apply all backtrace
-> (gdb) quit

Two issues with that pastebin: 1. I need Dolphin symbols. You might need to build Dolphin yourself to get them? 2. I need a stack trace while the PanicAlert is showing.

i just know that dolphin-emu in debug mode has itself symbols in totaldb.dsy and has ability of generating symbols map, and then can manually save as .map file.
May i use some of above stuffs in simple debugger, such as gdb, or must i build and then debug it in some IDE, such as Eclipse?

@hoangbathien: totaldb.dsy/map files contain symbols from games, not from Dolphin itself. We don't distribute symbol files for Linux builds, you need to build Dolphin yourself with CMAKE_BUILD_TYPE=Debug.

I built dolphin with CMAKE_BUILD_TYPE=Debug, then debugged with gdb. The report in http://pastie.org/10074981
The report was generated with the following procedures:
-> gdb dolphin-emu
-> (gdb) handle SIGSEGV pass noprint
-> (gdb) run

The program would start. Performed any actions necessary to reproduce the warning of
"unknown pointer 0x???????? 0x8011f8f8 LR 0x8011f8f8"
The question mark(?) in the warning represents a changable number as pressing OK button on warning pane for the next similar warning appeared but different numbers. But in this report i just got from starting dolphin-emu to the first warning encontered.
When the program hung but didn't crash i pressed ctrl+c in gdb. While the program was frozen and then continued with the next step
-> (gdb) backtrace full
-> (gdb) info registers
-> (gdb) x/16i $pc
-> (gdb) thread apply all backtrace
-> (gdb) quit
That's all!

Okay, that's what I was looking for; thanks.

Looks like the game is passing in "junk" as the address of a vertex array. And the address translation changes included some changes to make Memory::GetPointer much less tolerant of addresses where the expected behavior isn't obvious.

It seems kind of odd that Dolphin doesn't crash outright after showing the PanicAlert; not sure what's causing that. Maybe we should be doing the conversion lazily (don't convert until the vertex array is actually used)?

This should be fixed in latest master if my assumption is right.

https://dolphin-emu.org/blog/2015/06/01/dolphin-progress-report-may-2015/#40-6477-fix-invalid-pointers-by-phire

Great work! I was trying and the known problem of something "invalid pointer..." dissappeared at the first i had ever met before. But i need to check it through out the game to see if any issues like that happen.
Hope it work through!