NOW I know I'm doing something right:
Uncategorized
8
Posts
1
Posters
3
Views
-
NOW I know I'm doing something right:
*** Run-time problem MemoryAllocationFailed: INTERNAL/Extensions/Graham Nelson/Basic Inform.i7xd/Materials/Inter/BasicInformKit/RTPs
*** Memory allocation proved impossible.
*** Stack frame of 0 could not be created *** -
NOW I know I'm doing something right:
*** Run-time problem MemoryAllocationFailed: INTERNAL/Extensions/Graham Nelson/Basic Inform.i7xd/Materials/Inter/BasicInformKit/RTPs
*** Memory allocation proved impossible.
*** Stack frame of 0 could not be created ***Apparently this happens when I make the Table of Book Titles too long (more than 6 entries?)
-
Apparently this happens when I make the Table of Book Titles too long (more than 6 entries?)
I am pretty sure my table is not large enough to justify such an error, and upping the dynamic memory allocation limit seems to make no difference.
-
I am pretty sure my table is not large enough to justify such an error, and upping the dynamic memory allocation limit seems to make no difference.
I am extremely sure that I should be well outside the limits of the Z machine, but let me try building for Glulx.
-
I am extremely sure that I should be well outside the limits of the Z machine, but let me try building for Glulx.
Oh found https://intfiction.org/t/memory-allocation-error-z-code-vs-blank-story-tab-glulx/60213/4 that recommends the $OMIT_UNUSED_ROUTINES=1 flag for the inform6 compiler and that frees up enough space to fix the issue even in z8. Nice.
-
Oh found https://intfiction.org/t/memory-allocation-error-z-code-vs-blank-story-tab-glulx/60213/4 that recommends the $OMIT_UNUSED_ROUTINES=1 flag for the inform6 compiler and that frees up enough space to fix the issue even in z8. Nice.
OK, if I make the table even larger, the bug reappears. This is definitely an Inform7 compiler bug. I've gone through the code and I can see where the error is coming from: the use of a signed comparison where an unsigned would do makes everything blow up when the base pointer starts from a 16-bit SIGNED overflow. The stack error appears at the start with a ZERO SIZED allocation.
-
OK, if I make the table even larger, the bug reappears. This is definitely an Inform7 compiler bug. I've gone through the code and I can see where the error is coming from: the use of a signed comparison where an unsigned would do makes everything blow up when the base pointer starts from a 16-bit SIGNED overflow. The stack error appears at the start with a ZERO SIZED allocation.
I can understand why a signed comparison is made, but this needs to be fixed or we can't even make use of the entire available memory on the Z-machine. I'll try submitting a patch that does a DOUBLE check, one for a size overflow (to make sure that the new frame wouldn't change sign) and then the regular “out of stack” check, but unsigned.
I'll throw in an optimization for 0-sized allocations too. -
I can understand why a signed comparison is made, but this needs to be fixed or we can't even make use of the entire available memory on the Z-machine. I'll try submitting a patch that does a DOUBLE check, one for a size overflow (to make sure that the new frame wouldn't change sign) and then the regular “out of stack” check, but unsigned.
I'll throw in an optimization for 0-sized allocations too.And the pull request is up! Let's hope it get merged, this seems like a rather frustrating bug, I'm surprised so few people have come across it.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@babe It's the year of Linux on smartphone
-
@stefano I've been in your exact place! It's so frustrating! That reminds me, I need to tell my ISP to set my static IP via the ethernet port in my protectli and switch the Eero 6+ to bridged mode so I can control the firewall properly again. I've just been lazy. 😂
-
Vedi che ora va :D
Anni e anni fa cambiai la scheda wifi, in origine era solo wifi, poi ne misi usa col bluetooth ma fino ad oggi era senza antenna e quindi non prendeva niente neanche da vicino
-
Ho aggiunto anche l'antenna per il bluetooth visto che c'ero
-
-
@stefano residential line ?
Here in Belgium they filter out the ports 80/443 by default: "security measure".
> I even briefly asked an AI (I know, I know...),
to realize that it doesn't help. :)
-
Chi mai poteva rimontare un portatile senza collegare la ventola? 🤦
-
@simonett_a 💐🤗
