Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: Elliott Lee Newsgroups: scee.yaroze.beginners Subject: Re: Halting problem Date: Mon, 21 Sep 1998 12:16:16 -0700 Organization: Bwahaha Lines: 66 Message-ID: <3606A600.C79FE1FE@shell.jps.net> References: <36060A0C.97E@dma-design.com> <36061BEA.536E8D68@scee.sony.co.uk> <3606303C.869@dma-design.com> Reply-To: tenchi@shell.jps.net NNTP-Posting-Host: dhcp-m-62-237.cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.03 [en] (Win95; U) To be sure, when you're using SIOCONS, when you load your program to the Yaroze you should get 4 status messages for things like [.text] and [.data], etc. The exact addresses should be printed there. I also use a DATAMAN-like utility to make sure my addresses aren't colliding with each other especially when things are close together. If your program is all nicely broken up into functions and such, you may want to comment out the calls to the main routines and just leave initialization stuff in there. See if the program runs and then immediately exits without error. Following the advice about print statements, I usually have those statements in there as well. You could add the following variable at the top of your code: #define SHOW_DEBUG_STUFF and whenever you want a debugging statement in your code just put: #ifdef SHOW_DEBUG_STUFF printf( "DEBUG: Initializing Sound...\n" ); #endif So, that way during the creation stage, you can get debugging messages to track the progress of the program. And when you go for production, just comment out that #define SHOW_DEBUG_STUFF line and the printf statements won't be compiled in to the program, but they'll be there if you need to go back to them. Stuff that helps me out, - e! Brian Baird wrote: > > James Russell wrote: > > > > > > Looks like: > > > > o you've linked your code to some address that's lower than 0x8009000. That will wipe over the > > libraries, so that won't work. > > o you've got a bug in your code that occurs before you set up your screen display > > (TMD/TIM setup?) > > > > Try putting lots of "printf"s around the functions at the beginning of your program to see > > where it's crashing. If you put in a printf at the very start and you don't get any output, it's > > very likely that you're linking to the wrong place. > > I usually link to 0x8014000. Very first statement is a printf, and it > doesn't seem to get that far... I'll double check the linking tonight - > I had a gut feeling it might be something like that... > > The weird thing is that it worked *once*, I did a recompile/link without > changing anything & it stopped working - that's what made me think about > memory/link problems. > > -- > Brian @ DMA > > [ All opinions & views are my own, not DMA's, yadda, yadda, yadda ] -- Mata ne, ... ... - e! ::' tenchi@shell.jps.net ':: (Protocol) :: ACiD -/- ACS -/- pHluid -/- Yaroze -/- Nemesis :: (Tenchikun) ::. http://www.jps.net/tenchi .:: ''' '''