| Re: "Program code area full", even when trying to exit! [message #67177] |
Thu, 09 July 2009 16:43 |
Adam Solomon
Messages: 11
Registered: July 2009
|
Junior Member |
|
|
On Jul 9, 1:35 pm, David Fanning <n...@dfanning.com> wrote:
> Adam Solomon writes:
>> Come to think of it, I'm pretty sure there is. It would explain the "%
>> Stop encountered" I get every time I run it.
>
> Ah, could be on to something here. My theory
> is that if you type "RETALL" (RETurn ALL the way
> back to the IDL command line) before you run
> the program again, things should clear up for
> you.
>
> And, really, find yourself some different friends.
> The ones you've got don't have your interest at
> heart. :-)
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
IDL> RETALL
& END
^
% Program code area full.
When I used RETALL... but .full_reset worked! Thanks a lot! I'll make
sure my friends know how much trouble they've caused ;) Thanks again
for the help.
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67180 is a reply to message #67177] |
Thu, 09 July 2009 13:35  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Adam Solomon writes:
> Come to think of it, I'm pretty sure there is. It would explain the "%
> Stop encountered" I get every time I run it.
Ah, could be on to something here. My theory
is that if you type "RETALL" (RETurn ALL the way
back to the IDL command line) before you run
the program again, things should clear up for
you.
And, really, find yourself some different friends.
The ones you've got don't have your interest at
heart. :-)
Cheers,
David
--
David Fanning, Ph.D.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67181 is a reply to message #67180] |
Thu, 09 July 2009 13:27 |
Adam Solomon
Messages: 11
Registered: July 2009
|
Junior Member |
|
|
On Jul 9, 1:23 pm, David Fanning <n...@dfanning.com> wrote:
> Adam Solomon writes:
>> Hmmmm... well, I'm pretty sure I'm using a standard version of IDL,
>> not some ancient version. It's a piece of code that I just call with
>> "progname,input1,input2", etc. Maybe it's doing something funny with
>> memory allocation, I'll have to check with people who know more about
>> it and get back to you..... so is there a way to empty the program
>> code area? :)
>
> Another idea. This doesn't have a STOP statement
> in the code somewhere, does it? Maybe before the
> final END or RETURN? I could maybe see running a
> program over and over without it really completing
> itself causing an error like this.
>
> Cheers,
>
> David
>
> --
> David Fanning, Ph.D.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Come to think of it, I'm pretty sure there is. It would explain the "%
Stop encountered" I get every time I run it.
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67182 is a reply to message #67181] |
Thu, 09 July 2009 13:23 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Adam Solomon writes:
> Hmmmm... well, I'm pretty sure I'm using a standard version of IDL,
> not some ancient version. It's a piece of code that I just call with
> "progname,input1,input2", etc. Maybe it's doing something funny with
> memory allocation, I'll have to check with people who know more about
> it and get back to you..... so is there a way to empty the program
> code area? :)
Another idea. This doesn't have a STOP statement
in the code somewhere, does it? Maybe before the
final END or RETURN? I could maybe see running a
program over and over without it really completing
itself causing an error like this.
Cheers,
David
--
David Fanning, Ph.D.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67183 is a reply to message #67182] |
Thu, 09 July 2009 13:20 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Adam Solomon writes:
> Hmmmm... well, I'm pretty sure I'm using a standard version of IDL,
> not some ancient version. It's a piece of code that I just call with
> "progname,input1,input2", etc. Maybe it's doing something funny with
> memory allocation, I'll have to check with people who know more about
> it and get back to you..... so is there a way to empty the program
> code area? :)
Not sure. I've never managed to get it full. :-)
Try this:
IDL> .full_reset
Cheers,
David
--
David Fanning, Ph.D.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67184 is a reply to message #67183] |
Thu, 09 July 2009 13:07 |
Adam Solomon
Messages: 11
Registered: July 2009
|
Junior Member |
|
|
On Jul 9, 12:56 pm, David Fanning <n...@dfanning.com> wrote:
> Adam Solomon writes:
>> I'm pretty new to IDL, and mostly using it to run routines others have
>> written right now.
>
> This is your first major mistake, right here.
> You are hanging out with entirely the wrong people! :-)
>
>> I'm running a code which plots data, in a way that
>> I'm checking and comparing plots pretty often, so running the plot a
>> few times a minute or so. Pretty often (a few times an hour, I'd say)
>> I get a "Program code area full" error, and most of the time when it
>> happens, I can't even exit IDL! I type in "exit" and get the exact
>> same error.
>
>> This isn't an issue that other people using this routine have.
>
>> Any idea what could be going on?
>
> The "program code area" is a piece of memory that
> is set aside to compile IDL procedures and functions
> into the "bytecode" that runs faster in IDL. Just
> about the only time it is possible to get the code
> area full if if you try to run one monster IDL program,
> with no procedures or functions, from the IDL command
> line. You're not doing *this*, are you? ;-)
>
> I really have no idea how you are doing this. The program
> code area is suppose to be dynamically allocated now, so
> I haven't seen this error message in probably 10 years or
> so. This leads me to think you are either using a very
> old version of IDL, or you are doing something extremely
> unique. If the latter, I would love to know what it is. :-)
>
> Tell us more about how you are running the IDL code
> you are using.
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Hmmmm... well, I'm pretty sure I'm using a standard version of IDL,
not some ancient version. It's a piece of code that I just call with
"progname,input1,input2", etc. Maybe it's doing something funny with
memory allocation, I'll have to check with people who know more about
it and get back to you..... so is there a way to empty the program
code area? :)
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67185 is a reply to message #67184] |
Thu, 09 July 2009 13:02 |
pgrigis
Messages: 436
Registered: September 2007
|
Senior Member |
|
|
Adam Solomon wrote:
> Hi,
>
> I'm pretty new to IDL, and mostly using it to run routines others have
> written right now. I'm running a code which plots data, in a way that
> I'm checking and comparing plots pretty often, so running the plot a
> few times a minute or so. Pretty often (a few times an hour, I'd say)
> I get a "Program code area full" error, and most of the time when it
> happens, I can't even exit IDL! I type in "exit" and get the exact
> same error.
>
> This isn't an issue that other people using this routine have.
I have no idea what that means, but that sounds so like
a 1980's error message... Are you by any chance using
an ancient version of IDL?
Ciao,
Paolo
>
> Any idea what could be going on?
|
|
|
|
| Re: "Program code area full", even when trying to exit! [message #67186 is a reply to message #67185] |
Thu, 09 July 2009 12:56 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Adam Solomon writes:
> I'm pretty new to IDL, and mostly using it to run routines others have
> written right now.
This is your first major mistake, right here.
You are hanging out with entirely the wrong people! :-)
> I'm running a code which plots data, in a way that
> I'm checking and comparing plots pretty often, so running the plot a
> few times a minute or so. Pretty often (a few times an hour, I'd say)
> I get a "Program code area full" error, and most of the time when it
> happens, I can't even exit IDL! I type in "exit" and get the exact
> same error.
>
> This isn't an issue that other people using this routine have.
>
> Any idea what could be going on?
The "program code area" is a piece of memory that
is set aside to compile IDL procedures and functions
into the "bytecode" that runs faster in IDL. Just
about the only time it is possible to get the code
area full if if you try to run one monster IDL program,
with no procedures or functions, from the IDL command
line. You're not doing *this*, are you? ;-)
I really have no idea how you are doing this. The program
code area is suppose to be dynamically allocated now, so
I haven't seen this error message in probably 10 years or
so. This leads me to think you are either using a very
old version of IDL, or you are doing something extremely
unique. If the latter, I would love to know what it is. :-)
Tell us more about how you are running the IDL code
you are using.
Cheers,
David
--
David Fanning, Ph.D.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
