Re: Strange errors
- From: "Steven Lord" <slord@xxxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 23:10:24 -0400
"Matthew Sullivan" <nospam@xxxxxxxxx> wrote in message
news:fgdr8d$me2$1@xxxxxxxxxxxxxxxxxxxxx
ImageAnalyst <imageanalyst@xxxxxxxxxxxxxx> wrote in message
<1193884363.080919.312120@xxxxxxxxxxxxxxxxxxxxxxxxxxx>...
*snip*
I am 100% sure that negative is never null. When I look at
it, it is always a list of positive numbers. Furthermore,
when I just cut and past the last command it works without
problem.
I turned JIT off and I still get the randomly get these
errors. It has become so bad that I can't run scripts for >
20 files without always getting these errors.
Type "dbstop if error" without the quotes at the prompt, then run your code.
When you receive an error, you'll enter debug mode (the K>> prompt). From
there, you can see the line where the error is thrown and examine the exact
contents of the variables as they exist at the time that line is executed.
Double-check that all the variables you use as indices on that line contain
positive integers or logicals. Once you've finished your investigation, use
"dbquit" to exit debug mode and "dbclear all" to remove the condition that
caused you to enter debug mode when you received an error.
--
Steve Lord
slord@xxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Strange errors
- From: Matthew Sullivan
- Re: Strange errors
- References:
- Re: Strange errors
- From: ImageAnalyst
- Re: Strange errors
- From: Matthew Sullivan
- Re: Strange errors
- Prev by Date: enter password
- Next by Date: Re: Numerical evaluation of single integral
- Previous by thread: Re: Strange errors
- Next by thread: Re: Strange errors
- Index(es):
Relevant Pages
|