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
Posted on 03-25-20 01:07 AM (rev. 3 of 03-25-20 01:08 AM) Link | #1554
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:)
  • Fedora Linux 31
  • [9F1B9DE4] melonDS 0.8.3 official binary
  • [7EE7F0A2] romlist.bin
  • from emuparadise:
    • [F24508AA] 0223 - Animal Crossing - Wild World (U)(SCZ).nds (33554432B)
    • [1280F0D5] bios7.bin (16384B)
    • [2AB23573] bios9.bin (4096B)
    • [B10CDB9F] firmware.bin (262144B)

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
Posted on 03-25-20 02:14 AM (rev. 2 of 03-25-20 02:31 AM) Link | #1555
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
Posted on 03-25-20 07:51 AM Link | #1557
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
Posted on 03-25-20 11:19 PM (rev. 2 of 03-25-20 11:19 PM) Link | #1560
Posted by Arisotura
still, good to know -- melonDS should fail gracefully if it doesn't have enough access, rather than crashing like that.


"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.
[powered by Acmlm] Acmlmboard 2.064 (2018-07-20)
© 2005-2008 Acmlm, Xkeeper, blackhole89 et al.