There is already a whole trace infrastructure apart from the debugger.

Please note the debugger IS eventually for interaction.

And I've shown you already 3 approaches, with varying details and footprint

• print when you break back to prompt {
• print whenever you pass a certain point with a or b
• print whenever you execute any statement with w

> push @DB::typeahead, \"a 119 p \$var\";

Please note again that a , b and w only take real Perl code

but p is a debugger command

Commands accepting debugger commands are documented with db_cmd or db_command

  DB<27> h {
{ db_command    Define debugger command to run before each prompt.
{ ?            List debugger commands to run before each prompt.
{{ db_command    Add to the list of debugger commands to run before ea
+ch prompt.
{ *             Delete the list of debugger commands to run before eac
+h prompt.
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.