[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debugging failure

From: Ólafur Jens Sigurðsson
Subject: Re: debugging failure
Date: Mon, 26 Nov 2007 12:22:50 +0100
User-agent: Mutt/1.5.16 (2007-06-11)

On Sun, Nov 25, 2007 at 09:06:08PM -0500, John Swensen wrote:
> On Nov 25, 2007, at 6:05 PM, Ólafur Jens Sigurðsson wrote:
>> On Sun, Nov 25, 2007 at 10:32:09PM +0100, David Bateman wrote:
>>> I think you want "dbstop('pkg',1)" instead
>> If I do that then I get the following:
>> octave:36> dbstop('pkg',1)
>> ans =  179
>> octave:37> pkg('install', 'physicalconstants-0.1.2.tar.gz')
>> octave:38> dbwhere
>> error: dbwhere: must be inside of a user function to use dbwhere
>> so it doesn't stop on the breakpoint.
>> Any idea why that is?
>> Oli
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
> If you call dbstop and the line number specified is not a 'executable' 
> line, then it will set the breakpoint at the next executable line.  If you 
> opened up the pkg.m file, I would suspect that the first executable line is 
> 179.  And to find a list of the breakpoints, you should use dbstatus.  
> dbwhere is used when in debug mode to find out where you are at.

Ok, so what I did should have stopped on line 179 in the pkg.m file
but didn't by some reason. Any idea what might have happend there?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]