Re: Strange errors



"Steven Lord" <slord@xxxxxxxxxxxxx> wrote in message
<fge4f0$126$1@xxxxxxxxxxxxxxxxxx>...

"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



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

.



Relevant Pages

  • Re: Strange errors
    ... when I just cut and past the last command it works without ... I turned JIT off and I still get the randomly get these ... Type "dbstop if error" without the quotes at the prompt, ... you'll enter debug mode. ...
    (comp.soft-sys.matlab)
  • Re: Operands to the || and && operators must be co
    ... % -or- enter the debug mode right after the first command ... Operands to the || and && operators must be convertible to logical ... convertible to logical scalar values.' ...
    (comp.soft-sys.matlab)
  • Warning: "Project will be debugged with specific security permissions"
    ... my project and run in debug mode. ... command line arguments are not be passed to the ... I installed the latest Managed DirectX SDK (I think it's ... Clicking NO cancels the execution ...
    (microsoft.public.vsnet.debugging)
  • Re: -Crawl- YAOODD: Thog the Ogre Fighter
    ... Darshan Shaligram wrote: ... > will know and love this command). ... > rather not use Ctrl-D if possible. ... as I never used debug mode. ...
    (rec.games.roguelike.misc)
  • Re: VARY too many devices offline
    ... Personally, I'd view this as a management issue, not a technical issue. ... The root problem in my opinion was the need for an operator to issue the ... command in the first place. ...
    (bit.listserv.ibm-main)