#277 Debugger slowdowns with large string variables

v0.4.x
closed-fixed
Debugger (177)
5
2006-10-01
2006-08-04
Jan Ploski
No

EPIC retrieves values of all variables after every
debugging step. This leads to extreme slowdowns or even
crashes if any variable's content extends several
kilobytes.

At present, I don't see a way to ask perl -d for a
variable's length before dumping the actual content, or
to get only the start of the content. However,
implementing support for excluding variables from being
dumped may be a reasonable workaround.

See https://sourceforge.net/forum/message.php?
msg_id=3853044 for a description of an actual problem
caused by this bug.

Discussion

  • Matthew Twomey

    Matthew Twomey - 2006-09-28

    Logged In: YES
    user_id=1578192

    Or how about a method to get a variable's value upon request
    instead of at each step?

     
  • Jan Ploski

    Jan Ploski - 2006-10-01

    Logged In: YES
    user_id=86907

    The main reason of the slowdowns turned out to be not the
    amount of data exchanged between perl -d and EPIC, but the
    inconsiderate use of regular expressions in the latter.

    Fixed in 0.4.13/0.5.11

     
  • Jan Ploski

    Jan Ploski - 2006-10-01
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks