Hi, guys,
Update: I am sorry, it's not the nesemu's fault. Problem solved. I met four strange problems when I tried to execute the latest nesemu 0.2 for Dingux:
1. I found if I enable the IPU in zImage, nesemu will cause segment fault 100% even though I am in telnet mode or use dmenu0.3,
Maybe IPU will occupy about 4MB memory? 2. dmenu 0.4 will crash the nesemu, it's known.
Still more memory compared with the dmenu 0.3? 3. Well, disable IPU and it works well if you execute it in telnet. However, If I use GDB to execute it in telnet, it will display segment fault in memset() function. (I think the latest version of nesemu is complied with the debug parameter, thank you. )
GDB will eat some memory...4. When the nesemu is running (Just the GUI, no game is runing), the whole system becomes quite slow (You can comment the dmenu in /sbin/main file, and add nesemu to /sbin/main/. Now the terminal cursor should be released, then you can use "top" to see sth. Maybe you want to execute it using "nesemu &", but the system will become much slower than the previous case, you can do nothing.). I tried to edit one file via vim, and vim almost freezed.
Memory again.Don't you think the memset() is the source of problems? Or nesemu is very memory-hungry? Maybe it's better to decrease the size of memory assigned to memset(). What do you think about these strange problems? Thank you for your suggestions because I still prefer the dmenu0.4.
