Path: news.mathworks.com!newsfeed-00.mathworks.com!NNTP.WPI.EDU!elk.ncren.net!newsflash.concordia.ca!canopus.cc.umanitoba.ca!not-for-mail
From: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson)
Newsgroups: comp.soft-sys.matlab
Subject: Re: Error lands in debugger instead?
Date: Tue, 9 Oct 2007 17:28:10 +0000 (UTC)
Organization: National Research Council Canada - Conseil national de rechereches Canada
Lines: 11
Message-ID: <fegdna$aeu$1@canopus.cc.umanitoba.ca>
References: <feg1fq$ptf$1@fred.mathworks.com> <feg29n$ag6$1@fred.mathworks.com> <feg9pk$95b$1@fred.mathworks.com>
NNTP-Posting-Host: origin.ibd.nrc.ca
X-Trace: canopus.cc.umanitoba.ca 1191950890 10718 192.70.172.160 (9 Oct 2007 17:28:10 GMT)
X-Complaints-To: abuse@cc.umanitoba.ca
NNTP-Posting-Date: Tue, 9 Oct 2007 17:28:10 +0000 (UTC)
Originator: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson)
Xref: news.mathworks.com comp.soft-sys.matlab:432043



In article <feg9pk$95b$1@fred.mathworks.com>,
Darik  <dgambleDEL@uwaterlooDEL.caDEL> wrote:
>Using dbstop if error will result in the debugger stopping 
>at the SET command, not at the line in the set function 
>causing the error. Does anyone know if there's a way to 
>have the debugger stop in the set function?

set() is normally a built-in function, not coded in matlab.

-- 
   "Okay, buzzwords only. Two syllables, tops."  -- Laurie Anderson