Code Limits in Eboot??

reefbarman · Post by **reefbarman** » Mon Jan 22, 2007 12:06 pm

Hey everyone,

i came across something really weird during writing my program, my program would refuse to run when i added two new functions in, i went over and over these functions and there was absolutely nothing wrong with them, i then got a hunch that maybe i had too many function and or code in my main.c file so i commented out some other function i knew worked but didnt really need and then compiled and it worked i was amazed, i then went about changing the functions i commented out to make sure it just wasnt a conflict with the first functions i commented out, and no matter which functions i commented out the program worked again, but i tried uncommenting everything and bang the program refuses to run again,

Is there some sort of limit to the amount of code that can be compiled into an eboot or kept in the one .c file?? im using 3.03oeb to test my program

reefbarman · Post by **reefbarman** » Mon Jan 22, 2007 12:16 pm

Just to confirm my suspicions i added more code into one of my functions, and bang it refuses to run again and just crashes the psp, how can i fix this break my code up into multiple files?? or is there just a limit that i can go past?

weltall · Post by **weltall** » Mon Jan 22, 2007 10:08 pm

most probably you have an allignment problem in your code. check if the variables which requires allignment are correctly alligned (like gu lists...)

reefbarman · Post by **reefbarman** » Mon Jan 22, 2007 10:35 pm

mmmmm im not using gu list or anything like that really, i am using OSLib but i havent had any problems with allignment with it before and the code i add isnt anything special just initializing variables and such mmmm i might swap some positions of things around though

J.F. · Post by **J.F.** » Tue Jan 23, 2007 4:36 am

I've seen PSP programs (without embedded roms or such) that were several megs in size (4.6M one was), so I seriously doubt there's any kind of size restriction beyond all the data fitting into the ~24M of RAM available. Maybe you have a compiler switch you're setting that switches on the MIPS equivalent to smallcode model. I don't know if the MIPS even has one, but it would be the first thing I'd think of on an x86 or 68k.

reefbarman · Post by **reefbarman** » Tue Jan 23, 2007 7:05 pm

mmm i still cant figure it out, im just using boring old cygwin and make files to compile it with maybe i have something bad in my makefile could that be it???? is there any other reason why when i add more code even just an empty for loop or if statement that it crashes the psp??? everything compiles fine

groepaz · Post by **groepaz** » Tue Jan 23, 2007 9:09 pm

listen to what weltall said, such behaviour is almost certainly caused by some alignment problem.

jockyw2001 · Post by **jockyw2001** » Tue Jan 23, 2007 10:07 pm

right and usually easy to debug with PSPLINK

reefbarman · Post by **reefbarman** » Wed Jan 24, 2007 12:16 am

okay what exactly is an allignment problem?? and im not using psplink should i be?

jockyw2001 · Post by **jockyw2001** » Wed Jan 24, 2007 12:29 am

http://www.devx.com/tips/Tip/13265

Psplink allows you to very comfortably run and debug PSP apps. Read the Psplink thread!

reefbarman · Post by **reefbarman** » Thu Jan 25, 2007 12:20 am

okay i dont know what happened but i ran my app through psplink and it worked then compiled it for kxploit eboots and it worked with out psplink too, very weird and i changed nothing in the code, anyways thank for you help and i have to say i LOVE psplink