it dont work it just says overflow
CrashSB
Root / Submissions / [.]
RaichuBenderCreated:
Download:JDEX3WNEVersion:1Size:
CrashSB
CrashSB is a program featuring a bug I discoverd.
What it does
It crashes SB (this also means unsaved data will be lost, so please save everything before doing this. YOU HAVE BEEN WARNED!). Then the 3DS error handler comes in and takes you back to the home menu and then restarts the system.
How to use it
This only works in edit mode. After running the program, the user will be prompted to enter CLEAR in direct mode. After that, They have to enter CRASH to crash SB.
How it works
It is pretty simple, yet confusing. This program defines three variables and a function called CRASH. Once the user clears the RAM and the executes the function, SmileBASIC doesn't know what to do and crashes. The confusing part is that normally when a variable is not defined, it will simply give an undifined variable error. CLEAR only works in direct mode, so that's why the user needs to type it in manually.
I discovered this glitch while working on a CHIP-8 intepreter.
Can this be exploited?
Turns out people are exploiting other bugs to launch the homebrew channel.
Fixed in 3.3.2.
RIP been patched
Thank goodness CONTROLLER 0 hasn't been patched!
uh it might be soon
But it isn't yet
yet
yes yet
Replying to:jamieyello
I made a program that crashed Petit computer once. Actually not really, I just corrupted a PTC file's header and turned it into a QR code. It saved but if you tried to run it Petit Computer would soft lock.
It's funny because ninjhax uses corrupted QR codes to work. I would wager if anyone gave a crap about DSi mode or DSi games there might be some potential exploit there.
Oh crap, I think you're on to something
I don't know exactly how but in the past week I crahed my 3ds twice. once, smilebasic shutted down, giving some kind of graphics crash log. The other time it completely crashed the console with an error from the ARM11 assembly language. I have filled 3 BG layers full on a screen of 128x127 tiles, but I dont think that's the reason directly. cuz i tried to do this on purpose afterwards, doing it 100 times in a for loop and it didnt cradh. So if ur searching for an even more extreme thing you may want to look into this.
Btw it also didn't give me such a nice dialog like in ur screenshot. just straight away black screen with printed text
Replying to:Ebbe
I don't know exactly how but in the past week I crahed my 3ds twice. once, smilebasic shutted down, giving some kind of graphics crash log. The other time it completely crashed the console with an error from the ARM11 assembly language. I have filled 3 BG layers full on a screen of 128x127 tiles, but I dont think that's the reason directly. cuz i tried to do this on purpose afterwards, doing it 100 times in a for loop and it didnt cradh. So if ur searching for an even more extreme thing you may want to look into this.
Btw it also didn't give me such a nice dialog like in ur screenshot. just straight away black screen with printed text
Probably coincidence.
Although there's still methods to crash 3.6.0 and JPN 3.6.3 easily.
Also, with custom firmware, it overwrites the exception handler, so stock firmware (or when disabling Luma's exception handler) shows that error message while CFW shows a more detailed screen showing raw processor values as well as a small stack dump, during the crash.
I do get that this screen appears spooky but I like the verbosity. A simple "An error has occured. plz reboot sweetie" is too vague for me