gnupic: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
Subject:
Re: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
From:
####@####.#### (Byron A Jeff)
Date:
13 Oct 2001 16:59:43 -0000
Message-Id: <200110131659.MAA21841@cleon.cc.gatech.edu>
>
> On Wed, Oct 03, 2001 at 10:30:18PM -0400, Byron A Jeff wrote:
> > However I've run into a problem. I'm using gpsim for testing. It had been
> > working just fine with the GUI until I added/moved quite a bit of code.
> > All of a sudden it starts segfaulting upon startup. Upon debugging I
> > discovered that it was failing on a malloc deep in the C library.
> >
> > But it's flaky. It works fine a time or two then a string of segfaults.
>
> I tried out Electric Fence, and found three bugs.
>
> In eXdbm.c:
> 167c167
> < DbmDbList = (TDbmDbList *) malloc(sizeof(DbmDbList));
> ---
> > DbmDbList = (TDbmDbList *) malloc(sizeof(TDbmDbList));
>
>
> For the bugs in gpsim, I made quick hacks. Scott, you should look
> at this:
> In src/cod.cc:
> 462c462
> < for(offset=0; offset<COD_BLOCK_SIZE; offset += COD_LS_SIZE) {
> ---
> > for(offset=0; offset<510; offset += COD_LS_SIZE) {
>
> In src/pic-processor.cc:
> 1263c1263
> < files[i].line_seek = new int[files[i].max_line];
> ---
> > files[i].line_seek = new int[files[i].max_line+1];
This last one was one of the failures that I was seeing. Let me make these
changes and test them out right quick. I'll be right back....
[And soon thereafter by the magic of E-mail time streching...]
...and it works like a champ! The machine where it crashed every time came
up just fine.
Thanks for the great work. While I'm here I have a couple of more questions
that may be easily answered here.
1) Is it possible to configure the GUI so that the same screens, layout and
geometry come up each time? Which screens pop up, their sizes, and their
screen positions all seem to be random.
2) Has anyone had trouble with the top part of the RAM screen no updating?
Sometimes the memory locations simply will not update. I can usually get it
going by bringing the screen down, bring it back up, and then do a couple
of step operations. But it's real inconsistent.
Thanks to gpsim I have almost all the 16 bit operations on my interpreter
tested. It's an outstanding tool.
BAJ
