Skip Menu |

This queue is for tickets about the Debug-Trace CPAN distribution.

Report information
The Basics
Id: 78370
Status: open
Priority: 0/
Queue: Debug-Trace
People
Owner: jv [...] cpan.org
Requestors: pause [...] tlinx.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.04
Fixed in: (no value)

History Show all quoted text
  Sat Jul 14 05:33:35 2012 pause [...] tlinx.org - Ticket created
Subject: no way to simply trace subroutines (all, by default).
This module is only as useful as putting printf in a subroutine, but less so, as you have to put it on the command line each time. I want to trace all subs in my file -- in any module in my file. I don't want to have to type 100 subroutines names out on the command line, nor multiple package names. Ltrace is probably more useful for most people who only use 1 module / file, but for those of us who have several-20 classes in the same file -- not modules, but using packages as classes as 'types', it's not very useful either. But having to remember my subnames...ouch... Impossible. I always end up instrumenting my code for tracing being able to turn arbitrary groupings off/on...but not so convenient when what I want is something 1 step above statement tracing -- just function call tracing...
  Sat Jul 14 11:43:46 2012 jv [...] cpan.org - Correspondence added
The purpose of Debug::Trace is to quickly add detailed tracing to a single subroutine, or a couple of routines, without having to modify program sources. There are other tools for other types of tracing.
  Sat Jul 14 11:43:46 2012 The RT System itself - Status changed from 'new' to 'open'
  Sat Jul 14 11:43:46 2012 jv [...] cpan.org - Status changed from 'open' to 'resolved'
  Sat Jul 14 11:43:46 2012 jv [...] cpan.org - Given to JV
  Sat Jul 14 23:43:21 2012 pause [...] tlinx.org - Status changed from 'resolved' to 'new'
  Sat Jul 14 23:51:25 2012 pause [...] tlinx.org - Correspondence added
Rather than simply saying there are other modules to do that type of tracing, why not name one? I'm saying that this module is missing the most basic ability of being able to trace 'any'. Not one, but just any module, please?? Can't you trace 'any' module? If you can't, they my issue remains... treat it as an RFE? Or refer the user to a module that can rather than saying there are other tools for that type of trace...ok...where?... I see 2 Modules related to debug tracing of subs. One only works for specific subs, the other only specific modules. Neither is general case or works for the general case. Seems like a obvious hole in 'Debug::Coverage' :-)... But just closing out a valid request saying there are other tools without mentioning them, or the idea that they should be included... how basic is a simple turn on tracing of all subs? (conceptually!, in practice...)
  Sat Jul 14 23:51:26 2012 pause [...] tlinx.org - Status changed from 'new' to 'open'
  Sun Jul 15 10:01:35 2012 jv [...] cpan.org - Correspondence added
On Sat Jul 14 23:51:25 2012, LAWALSH wrote: Show quoted text
> Rather than simply saying there are other modules to do that type of > tracing, why not name one?
Devel::CallTrace ?