summaryrefslogtreecommitdiffhomepage
path: root/mixlib/xmix_vm_handlers.c
AgeCommit message (Collapse)Author
2020-10-18Use g_error_freeJose Antonio Ortega Ruiz
2019-04-09Change vm->address_list from GSList to GQueueJose Antonio Ortega Ruiz
The current emulator uses an unbounded linked list for tracking the memory locations our program has traveled through. On a 64 bit system, this requires 16 bytes of data for every instruction a MIX program performs. For small programs that are light on computation cycles, this does not cause a noticeable issue. For programs that execute hundreds of millions of instructions, this causes the memory footprint of the virtual machine to explode. I have attached an example MIXAL program that will cause the VM to grow to over 3 GB of memory usage when run. To run the sample, compile coin-opt.mixal (attached), run it in mixvm, and enter 499 at the prompt. Or use the following steps. This patch changes all the appropriate references to GQueue references and also caps the backtrace at 1000, which can be changed in the mixlib/mix_vm.h header. I feel like 1000 is a reasonable limit for the vast majority of debugging needs. Most people are looking back at the most recent 100 instructions or so. You can get the original behavior (unlimited tracing) back by setting the MIX_MAXTRACE to -1, albeit with a slightly higher memory cost (24 bytes per instruction). Or you can turn it off entirely by setting it to 0. Using a queue doesn't change the logic of the program in any significant way, and it allows programs to run for an extended period of time without consuming all the memory on the machine and slowing down to a crawl. -Kevin Brunelle
2014-08-03Apparently tautological comparisons fixed (bug #42871)jao
2014-05-21Avoiding format strings security warnings (cf. #8467)Jose Antonio Ortega Ruiz
2010-09-27Fix for off-by-one bug in I-register modification breakpointsJose Antonio Ortega Ruiz
2007-06-25GPL v3 noticesJose A Ortega Ruiz
git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-43
2006-08-08External programs management improvementJose Antonio Ortega Ruiz
- External programs (editor and mixasm) execution is more robustly controlled both in mixvm and gmixvm. - In gmixvm the external programs dialog has been revamped: - Only proper paths can be introduced for the executables (via a graphical file chooser). - Flags for mixasm are no longer free text, but a check button. - Internally, the code has been refactored. git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-28
2006-08-05Bug fix: mixvm's smem correctly handles negative zeroJose Antonio Ortega Ruiz
git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-11
2006-08-05Bug fix: typo in cbpo help stringJose Antonio Ortega Ruiz
git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-10
2006-03-24CVS $Id$ tags removed.Jose Antonio Ortega Ruiz
git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-7
2006-03-20Version 1.2.1 imported1.2.1Jose Antonio Ortega Ruiz
git-archimport-id: mdk@sv.gnu.org/mdk--devel--1--patch-1