[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Expected behaviour of dbtype
From: |
Richard Crozier |
Subject: |
Expected behaviour of dbtype |
Date: |
Tue, 23 Feb 2016 13:35:15 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Hello,
The help for dbtype states:
"When called with no arguments in debugging mode, display the script
file currently being debugged."
From this I expected that dbtype would print the function currently
stopped in the stack. So for instance, if I'm stopped in a function foo
which is called by a function bar, and I navigate up to bar by doing
dbup, I would have expected that dbtype would now print out bar.
However, as far as I can tell, it still prints out foo no matter where I
navigate too.
Is this the expected behaviour of dbtype, or a bug?
Richard
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
- Expected behaviour of dbtype,
Richard Crozier <=