Ticket #1471 (reopened defect)
Can I see a call stack?
| Reported by: | SvenDowideit | Owned by: | SvenDowideit |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Debugger for Perl 5 | Version: | 0.96 |
| Keywords: | Cc: |
Description
I really like to see where I am :)
Change History
comment:3 Changed 4 months ago by SvenDowideit
- Status changed from closed to reopened
- Resolution fixed deleted
the current line of code is _not_ the same as a stack
When I'm debugging some complex code, I'm looking to see each function call that lead to the current one - just like in Carp / die, but most debuggers add the ability to click on the stack, and give information about local variables at those points.
comment:4 Changed 4 months ago by bowtie
sorry
do you mean - Stack backtrace
Here's an example of what a stack backtrace via T command might look like:
. = ExSewi::wh('foo') called from file '/usr/src/Padre/Padre-Plugin-Debug/scripts/sewi.pl' line 20
As in button T => stack back-trace
see http://perldoc.perl.org/perldebug.html -> Stack backtrace, for .$@
take a look at the options with -> o => Display all options
I think you need to look at option frame but changing options, dose have side affects, you have been warned :)
you can change options with Raw

see -> http://padre.perlide.org/trac/wiki/Features/Perl5Debugger#CodeListing
if you use dot '.'
it will display the current debugger position ( as in next line to debug ) in Padre as current file with cursor on appropriate line.
nb, check you are using absolute filenames