From: Gerrit Van Damme on
Dear all,

I'm trying to debug a m-file but I'm unable to do this.
When I set a breakpoint in the Matlab Editor. The red dot is placed in the margin but is directly removed again. I've looked everywhere but can't find any info on this problem.
Any of you guys has an idea?

Regards,

Gerrit
From: Sean on
"Gerrit Van Damme" <gvd(a)mgb-tech.com> wrote in message <hsu0g1$om6$1(a)fred.mathworks.com>...
> Dear all,
>
> I'm trying to debug a m-file but I'm unable to do this.
> When I set a breakpoint in the Matlab Editor. The red dot is placed in the margin but is directly removed again. I've looked everywhere but can't find any info on this problem.
> Any of you guys has an idea?
>
> Regards,
>
> Gerrit

One possibility is that you're already in debug mode.
>> dbquit %maybe a few times
Then try it.
From: Gerrit Van Damme on
Thanks Sean for the fast response but it's not working.

greets,

Gerrit

>> dbquit
??? Error using ==> dbquit
Debugging commands are only allowed in debug mode.
From: Walter Roberson on
Gerrit Van Damme wrote:

> I'm trying to debug a m-file but I'm unable to do this.
> When I set a breakpoint in the Matlab Editor. The red dot is placed in
> the margin but is directly removed again. I've looked everywhere but
> can't find any info on this problem.

Removed as soon as you click to place it? That could occur if the
routine is already executing. Removed as soon as you start the routine?
That would occur if you have 'clear all' or some other 'clear' statement
in the routine.
From: Gerrit Van Damme on
Walter Roberson <roberson(a)hushmail.com> wrote in message <ubxIn.11216$wV.1151(a)newsfe11.iad>...
> Gerrit Van Damme wrote:
>
> > I'm trying to debug a m-file but I'm unable to do this.
> > When I set a breakpoint in the Matlab Editor. The red dot is placed in
> > the margin but is directly removed again. I've looked everywhere but
> > can't find any info on this problem.
>
> Removed as soon as you click to place it? That could occur if the
> routine is already executing. Removed as soon as you start the routine?
> That would occur if you have 'clear all' or some other 'clear' statement
> in the routine.

It's removed as soon as I click to place it.
Thing is nothing is executing at that moment...
Is there a killall command?