On Sat, Sep 27, 2025, at 3:32 PM, Bernd Paysan wrote: > Am Samstag, 27. September 2025, 13:56:10 Mitteleuropäische Sommerzeit schrieb > Ethan Azariah: >> I can't reproduce it on my 64-bit tablet either, and I regularly use lines >> like this in 0.7.0. Of my various devices, the problem only occurs on a >> 32-bit x86 tablet, Android 7.1.2 (LineageOS 14.1), Gforth 0.7.9_20250305. >> I'm very surprised to have got a 32-bit tablet, but now I have and the >> older, rooted Android is good for tinkering. >> >> I remember from years ago some weird heisenbug affected only a 32-bit >> Android device. Do we want to track it down or do you just want to call >> 32-bit obsolete? I don't mind; Gforth is convenient but a bit too complex >> for me to really get into. I could run debugging binaries images or >> whatever if you want to supply them, but I don't want to use the Android >> SDK and I'm not yet used to using a debugger. > > It should be sufficient to look at what > > ORDER > > prints out. It should be > > Forth Forth Root Forth
I put in `order` as a debug print before the block was loaded. The bug appeared whether the first item was `editor` (default in my startup sequence) or `Forth` (set by `only forth also`). The bug has disappeared now I've moved the loading of the qxv block to before the editor. I can't see any reason why it should have disappeared, nor why it appeared in the first place. This is why I think 32-bit Gforth has, in recent years, got a bug not present in 64-bit. The last time I used Gforth on 32-bit Android, there was a similar bug with code not working which worked everywhere else or started to work when I changed something irrelevant. At the time, I didn't think it was worth fixing and I can't get details now because that device is broken.
