Menu
▾
▴
Re: [fuse-emulator-devel] Is Fuse alive (and where)?
|
From: desertkun <des...@gm...> - 2025-09-15 12:37:09
|
Let's meet here https://discord.gg/8Bbx3Vrc this is a popular ZX Spectrum server On Mon, Sep 15, 2025, 14:31 Joerg Pleumann <joe...@gm...> wrote: > I just gave it a quick try. It has trouble with the way I am invoking the > application (via open -a FuseX.app --args ...), probably due to a missing > permission request for the file system („Operation not permitted“). The > original, older Fuse for Mac did not have this. I’ll create a ticket in > your GitHub project. Normal operation is fine, including loading things via > the open file dialog. > > Am 15.09.2025 um 13:31 schrieb desertkun <des...@gm...>: > > Hello. I've been semi-maintaining a fork of Fuse called FuseX on > speccytools.org > > It has gdbserver stub built in, so you can connect to it with with > z88dk-gdb and do things like inspect memory, place breakpoints, observe > stack, and if your debugger supports (z88dk-gdb does, but it must be built > by z88dk), show source code mapping to that. I believe this should work > with z80-binutils, however I have not tested that. > > You enable gdbserver in settings and connect with your gdb of choice, of > which z88dk-gdb is the only one really tested. > > On Mon, Sep 15, 2025, 13:25 Joerg Pleumann <joe...@gm...> > wrote: > >> Hi Phil, >> >> thanks a lot for the response — and for all the hard work and dedication >> that went into Fuse since it was conceived in 1999. Apart from CSpect, >> which I use for Next-specific stuff, Fuse has been my favorite 48K/128K >> emulator for a long time now, especially due to the fact that it’s >> available on so many platforms. >> >> I agree Fuse is quite mature, but, as you mentioned, platforms move on >> and software may have to adapt from time to time in order not not become >> obsolete. I’m not sure how much assistance I could provide here, but I’m >> definitely willing to test and provide feedback. I regularly use Intel and >> Arm Macs as well as Ubuntu machines. >> >> I already tried to build the latest Mac version, with the intention of >> getting a bit of understanding of the code base and maybe solving my little >> issues locally, then provide a patch, but so far I even failed to checkout. >> Is there a chance you establish contact with Frederick Meunier, so I can >> ask him a few questions? >> >> Best regards >> Joerg >> >> Am 15.09.2025 um 11:49 schrieb Philip Kendall <ph...@sh... >> >: >> >> > Did everybody move on to other things or is it because the project is >> so mature (almost) no changes are needed? :) >> >> [ Wakes up from slumber ] >> >> I'd say both. Certainly from my point of view, I'm at a very different >> stage of my life than I was in 1999 when the project started and I'm pretty >> sure that will apply to a number of the other "core" developers as well. >> >> But I'd also agree that the project - and in fact, the software Spectrum >> emulation scene in general - has reached maturity; you can see this in that >> the rate of development of all the other major emulators has pretty stopped >> as well - because they do everything that 99% of users want to do, which is >> to play Manic Miner. The notable exception here is Spectrum Next emulation, >> but that is _such_ a different machine even if it uses a "CPU" which is a >> superset of the Z80. >> >> With regards to the macOS version in particular, we always had a single >> point of success of the one developer who owned a Mac; I'm not aware of >> anyone even vaguely active who is trying to make new macOS builds - and as >> you note, the evolution of the Apple hardware ecosystem means there's >> probably a lot of catching up to do. >> >> Please nobody let me be a blocker to getting things done with the project >> - I'm happy to talk about what privileges someone would need to get new >> releases out if there's someone who is genuinely interested in doing so. >> >> Thanks, >> >> Phil >> >> >> >> >> >> On Mon, Sep 15, 2025 at 8:15 AM Joerg Pleumann <joe...@gm...> >> wrote: >> >>> Hi Alberto, >>> >>> it’s a bit sad to hear that Fuse is stalled. Did everybody move on to >>> other things or is it because the project is so mature (almost) no changes >>> are needed? :) >>> >>> I am using Fuse as emulator in a multi-platform Z80 compiler environment >>> I’ve been developing for a while now. I have a couple of issues, including >>> a bigger one with multi-line debugger commands fed into Fuse via the >>> command line. In the meantime, I’ve been able to solve the latter, but >>> would still prefer a more „solid“ solution. From the back of my head, >>> here’s my full list of issues/questions: >>> >>> 1) Could there be an alternative --debugger-command-file that points to >>> a file containing the debugger commands? If there are many and complex >>> breakpoints the command line gets extremely long, and those newlines scare >>> me a lot when pushing everything though my tools and a shell process until >>> it arrives in Fuse. >>> >>> 2) As an alternative idea to 1): The CSpect emulator uses certain >>> invalid opcodes (such as $dd $01) as breakpoints. That means the opcodes >>> would be part of the program itself and not have to be specified on the >>> command line. Is that something you could consider? >>> >>> 3) Could the default behavior for 128K .sna files be changed? Currently >>> the system interprets them as Pentagon snapshots, does not find the ROMs (I >>> am not interested in Pentagon) and „crashes“ into a 48K machine. I >>> understand this is possibly a „historical decision“, but in my opinion >>> there’s nothing inherently Pentagon about the format. Would something like >>> this work: If the Pentagon ROMs are not there and/or the user specified >>> —machine 128 on the command line, treat this as a 128K snapshot, not as >>> Pentagon? Or simply a checkbox in the preferences? >>> >>> 4) Could there be a „step over“ button in the debugger UI that basically >>> does what „n“ does in the debugger commands (as a convenience)? >>> >>> 5) Last but not least, the Mac version seems to be a bit behind the >>> latest upstream (and have some bugs of its own). Not sure if the main Mac >>> developer is on this list, but is there a chance for an update? I’m very >>> much willing to provide feedback for Intel and Arm Macs. I could also try >>> building either locally, but I probably won’t be much help with the actual >>> development because I don’t know the codebase. >>> >>> Best regards >>> Joerg >>> >>> > Am 14.09.2025 um 23:58 schrieb Alberto Garcia <be...@ig...>: >>> > >>> > On Sun, Sep 14, 2025 at 10:32:08AM +0200, Joerg Pleumann wrote: >>> >> sorry for using the developer list for this question, but since all >>> >> the other places (especially the SourceForge project for Mac Fuse, >>> >> which is the flavor I am using) are so inactive, I was wondering >>> >> if the project might have moved elsewhere. Is there a Discord or >>> >> another place where one might ask questions, or are things really as >>> >> inactive as they seem? >>> > >>> > You can ask questions here, I guess, but the project is certainly >>> > stalled at the moment... >>> > >>> > Berto >>> > >>> > >>> > _______________________________________________ >>> > fuse-emulator-devel mailing list >>> > fus...@li... >>> > https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel >>> >>> >>> >>> _______________________________________________ >>> fuse-emulator-devel mailing list >>> fus...@li... >>> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel >>> >> >> _______________________________________________ >> fuse-emulator-devel mailing list >> fus...@li... >> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel >> > > |
