BX-24 Ram usage

Started by Paul J. Smith August 7, 2005
Hello,

I've been having some issues with my code hanging. Even though the
compiler says I've used around 280 bytes of ram, I tried a utility
called ramalyzer which states I could be using up to 434.

Could it be that I've run out of RAM? Is this the type of issue that
can be expected when this happens?

Thanks.



I have just had the same problem. Many BasicX functions use
incredible amounts of stack space. In my case I am using some of
those functions and I also have 2 serial ports. Everything was
working well until I lengthened the input queue of the port used for
input and also lengthened the output queue for the output port.
While my static usage of ram was well less than the maximum, I think
I ran out of stack space. It crashes regularly, and I need to reduce
the queue lengths. This makes me think, as I sit here, If one serial port is exclusively
for output and the other port is exclusively for input, could I not
use the input half for a separate device from the output half? I
will make a new thread about this.

As for your case, I suspect the stack is the problem. Try using
BxDism which is referrer-to here frequently. It seems like a great
resource. I will be using it for my project today.

-Tony

--- In basicx@basi..., "Paul J. Smith" <pjsmith@m...> wrote:
> Hello,
>
> I've been having some issues with my code hanging. Even though the
> compiler says I've used around 280 bytes of ram, I tried a utility
> called ramalyzer which states I could be using up to 434.
>
> Could it be that I've run out of RAM? Is this the type of issue
that
> can be expected when this happens?
>
> Thanks.



Thanks for the endorsement Tony. Here is the link to bxDism:
http://home.austin.rr.com/perks/basicx/bxDism/

Mike

> I have just had the same problem. Many BasicX functions use
> incredible amounts of stack space. In my case I am using some of
> those functions and I also have 2 serial ports. Everything was
> working well until I lengthened the input queue of the port used for
> input and also lengthened the output queue for the output port.
> While my static usage of ram was well less than the maximum, I think
> I ran out of stack space. It crashes regularly, and I need to reduce
> the queue lengths. > This makes me think, as I sit here, If one serial port is exclusively
> for output and the other port is exclusively for input, could I not
> use the input half for a separate device from the output half? I
> will make a new thread about this.
>
> As for your case, I suspect the stack is the problem. Try using
> BxDism which is referrer-to here frequently. It seems like a great
> resource. I will be using it for my project today.
>
> -Tony
>
> --- In basicx@basi..., "Paul J. Smith" <pjsmith@m...> wrote:
> > Hello,
> >
> > I've been having some issues with my code hanging. Even though the
> > compiler says I've used around 280 bytes of ram, I tried a utility
> > called ramalyzer which states I could be using up to 434.
> >
> > Could it be that I've run out of RAM? Is this the type of issue
> that
> > can be expected when this happens?
> >
> > Thanks.
>