You are not logged in.
Pages: 1
Hi,
I see a bunch of warnings come up in the dev console window... how do I know when/where in execution they occurred? Can I break on warning, or can it be logged somehow?
I see the wiki mentions modifying the source code and then dumping enormous trace logs... is this the only solution?
Thanks!
Last edited by Kajitani-Eizan (2013-01-15 19:27:49)
Offline
find the print statement that does the warning youre interested in, debug it in visual studio, and put a breakpoint on the warning. Thats how I'd do it. Then you can inspect various values like NDS_ARM9.R to see the registers state.
Offline
How to do this? Do I load the solution from the source code, build, and then debug that? Or can I find the strings and virtual machine state when using the Attach to Process feature on the pre-compiled .exe? Also, it doesn't seem to compile cleanly from source (using VS2012 and converting the 2008 solution). Sorry, total newbie at complicated source code management/compiling.
Thanks!
Last edited by Kajitani-Eizan (2013-01-21 21:55:23)
Offline
knowledge of such things is prerequisite for the technical forum. but i can tell you, its 1/100 as hard as some other opensource projects to build and debug. unfortunately, 2012 isnt supported. 2010 will work if you build repeatedly until it finally works.
Offline
Pages: 1