tag:blogger.com,1999:blog-34057821.post1105418325384727655..comments2024-03-27T10:33:22.456+01:00Comments on Bilou HomeBrew's Blog: The latest devkitproPypeBroshttp://www.blogger.com/profile/10564522267743689261noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-34057821.post-20398856182041820742017-01-05T15:41:37.617+01:002017-01-05T15:41:37.617+01:00sp = 0 crash is there because some code in GameScr...sp = 0 crash is there because some code in GameScript::parseline[case 's'] decided to save sp's value at [sp+0] rather than in a register (as with "g++ 4.5.1"). that's already a bit odd: 'mov r3, r7' (with r7 playing the role of the stackframe base address) could have worked instead of 'ld r3, [r7,0]'. More odd is the fact that for some reason, the value in [sp+0] got trashed and no longer contains sp, but 0. Oddest is that it all happened when almost no code is run (just a call to siscanf), and never occur when there's a .spr file to load...<br /><br />could be worth investigating with the emulator if I ever manage to reproduce the issue.<br /><br />Issue happens when requesting an animation that is missing in the .spr file and parsing further (i.e. trying to create a state based on that animation).PypeBroshttps://www.blogger.com/profile/10564522267743689261noreply@blogger.com