Views: 6,702,286 | Homepage | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search | 03-29-24 05:24 AM |
Guest: |
0 users reading [solved] crash on Run iff romlist.bin is present | 1 bot |
Main - Compatibility / Testing - [solved] crash on Run iff romlist.bin is present | Hide post layouts | New reply |
squeegily |
| ||
Half-eaten melon Positive Schlub Level: 10 Posts: 1/23 EXP: 4222 Next: 192 Since: 03-25-20 Last post: 1432 days ago Last view: 1419 days ago |
Title says it all
When I try to Run anything after melonDS was launched in sight of the romlist, I get melonDS 0.8.3
http://melonds.kuribo64.net/ OpenGL: renderer: AMD TURKS (DRM 2.50.0 / 5.5.5-200.fc31.x86_64, LLVM 9.0.0) OpenGL: version: 3.3 (Core Profile) Mesa 19.2.8 Audio output frequency: 48000 Hz ARM9 BIOS loaded ARM7 BIOS loaded Segmentation fault (core dumped) This was tested with both the built-in "DS Menu" firmware, and ACWW#0223. Both crashed if the romlist was present. However, if melonDS was launched without access to the romlist, it complained on startup, but at least begun to run both without issue. (ft. filesize and crc32 where applicable to clear up possible ambiguities:)
I have not yet tested to see to what degree saving is broken (on the games I care about) without the romlist, but I'd assume this is something to be fixed, rather than "worked around" thus. If you need any more data, please ask and I'll do my best to oblige. |
squeegily |
| ||
Half-eaten melon Positive Schlub Level: 10 Posts: 2/23 EXP: 4222 Next: 192 Since: 03-25-20 Last post: 1432 days ago Last view: 1419 days ago |
Well. It seems my problem is: I'd put all the "system files" in the "system folder" (that users can't change) where the melonDS binary stood.
little did I realize that it requires to make changes to firmware.bin for basic operation (although it politely backs up the original copy first), and will die if it cannot. I had fooled myself into thinking the presence of the romlist was the problem—when, in fact, that was an artifact of my moving between the (write-protected) folder containing the romlist, and the user's folder without it… |
Arisotura |
| ||
Big fire melon magical melon girl Level: 55 Posts: 468/876 EXP: 1311342 Next: 2847 Since: 03-28-17 From: France Last post: 10 hours ago Last view: 10 hours ago |
still, good to know -- melonDS should fail gracefully if it doesn't have enough access, rather than crashing like that. we'll look into it, thank you for reporting. ____________________ Kuribo64 |
squeegily |
| ||
Half-eaten melon Positive Schlub Level: 10 Posts: 3/23 EXP: 4222 Next: 192 Since: 03-25-20 Last post: 1432 days ago Last view: 1419 days ago |
Posted by Arisotura "Ultimately", this should actually become irrelevant once an explicit "data folder" for storing the ini and [at least changes to] the firmware is chosen—as other robust programs (such as Minecraft and Firefox) do with their "internal configuration" data in fact, "not knowing anything else", I'd prefer to be warned / notified / see visible problems when, for whatever reason DS system settings (such as system nickname, and MAC) are unable to be saved. |
Main - Compatibility / Testing - [solved] crash on Run iff romlist.bin is present | Hide post layouts | New reply |
Page rendered in 0.022 seconds. (2048KB of memory used) MySQL - queries: 28, rows: 81/81, time: 0.013 seconds. Acmlmboard 2.064 (2018-07-20) © 2005-2008 Acmlm, Xkeeper, blackhole89 et al. |