Yah, the bugger again ;)
[action=Hellcat]has yet another problem....[/action]
Not uncommon theese days
OK, this is it:
First off, I'm in 3.xx kernel mode, no legacy 1.50.... (however, same crash on 1.50, I tried....)
I have this nice and shiny kernel .PRX that gave some headaches already.... so far it's loading fine and working.... somehow....
I have also setup a function in my (main) usermode .PRX that will handle some stuff (file IO) I can't do in the kernelmode .PRX due to 3.xx kernelmode restrictions.
So, the kernel .PRX calls the function in the user .PRX (I give the kernel .PRX the address of the function in the user .PRX at runtime - similar to like callbacks work - as a parameter to a function in the kernel .PRX that saves the pointer (to the user .PRX function) into a function definition/pointer....)
For debugging/testing, I am currently (trying) to printf() the filename and filesize instead of actually writing files.....
And that just kills the PSP O_O
It does a few printf's and crashes - boom.
If I comment out the printf() line, everthing runns smooth....
Is there a known issue with printing f's while kerneling in the backyard?
[action=Hellcat]hopes that one day good stuff will arise from so many q's....[/action]
Supplemental explanation to the weirdness described above:
In user .PRX I have:
int Blah(int bleh)
In kernel .PRX:
int Blah(int bleh);
int (*Blah) (int bleh)
kernelPrxFunctionToSavePo inter(void* func)
Blah = func;
Like said, the call to Blah() works fine, does everything it should, many, many, times, up to the end....
....as long as in Blah() are NO printf's, once those are in -> CRASHY