[Top][All Lists]

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

[Octave-bug-tracker] [bug #37574] odd behaviour of dbstep out

From: Richard
Subject: [Octave-bug-tracker] [bug #37574] odd behaviour of dbstep out
Date: Mon, 15 Oct 2012 10:01:17 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0


                 Summary: odd behaviour of dbstep out
                 Project: GNU Octave
            Submitted by: crobar
            Submitted on: Mon 15 Oct 2012 10:01:16 AM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Richard Crozier
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



Consider the behaviour shown in the set of attached files related to dbstep

When I set 


and am stopped on a warning statement running "dbstep out" acts like dbcont.
This is an issue in itself.

However, when I then set 


and add a breakpoint, the debugger does not stop in the function with the
break point, but instead acts as though I have called dbstep out immediately
on entering debug mode already and is stopped in the higher level function. 

It is best demonstrated in the supplied example which consists of three files,
the two function files


and a script dbstep_out_test.m which calls dbstepouttesthighlevel to
demonstrate the issue.


File Attachments:

Date: Mon 15 Oct 2012 10:01:16 AM GMT  Name: dbstep_out_test.m  Size: 433B  
By: crobar

Date: Mon 15 Oct 2012 10:01:16 AM GMT  Name: dbstepouttesthighlevel.m  Size:
164B   By: crobar

Date: Mon 15 Oct 2012 10:01:16 AM GMT  Name: dbstepoutlowlevel.m  Size: 170B  
By: crobar



Reply to this item at:


  Message sent via/by Savannah

reply via email to

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