Path: news.mathworks.com!not-for-mail
From: "Matthew Sullivan" <nospam@nospam.no>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Strange errors
Date: Sat, 3 Nov 2007 22:03:07 +0000 (UTC)
Organization: The MathWorks, Inc.
Lines: 54
Message-ID: <fgir6r$rvt$1@fred.mathworks.com>
References: <ffsuk8$331$1@fred.mathworks.com> <1193884363.080919.312120@22g2000hsm.googlegroups.com> <fgdr8d$me2$1@fred.mathworks.com> <fge4f0$126$1@fred.mathworks.com>
Reply-To: "Matthew Sullivan" <nospam@nospam.no>
NNTP-Posting-Host: webapp-02-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1194127387 28669 172.30.248.37 (3 Nov 2007 22:03:07 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Sat, 3 Nov 2007 22:03:07 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 1142155
Xref: news.mathworks.com comp.soft-sys.matlab:435954



"Steven Lord" <slord@mathworks.com> wrote in message
<fge4f0$126$1@fred.mathworks.com>...
> 
> "Matthew Sullivan" <nospam@nospam.no> wrote in message 
> news:fgdr8d$me2$1@fred.mathworks.com...
> > ImageAnalyst <imageanalyst@mailinator.com> wrote in message
> > <1193884363.080919.312120@22g2000hsm.googlegroups.com>...
> 
> *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@mathworks.com 
> 
> 

That was a useful tip, but again in debug mode everything
checks out (all positive integers).  Running the command
that sent me to debug mode in debug mode works fine.  I'm
still at a loss for what could be going on.  

As a possible workaround, is there an equivalent to the IDL
command (I'm really showing my roots) .continue?  That
wouldn't solve the root problem, but it stop it from
annoying me?

Thanks again,
Matt