I tried to make latest well-known GUI-enabled debugger ptkdb(version 1.1074) to work with perl-5.8.0+Tk-800.024

However, I did not succeed (although many other modules that I tried succeeded to be built, self-tested and installed).

Test and installation of a module was okay, but when I tried to use it I got folowing:

D:\Work\PerlScripts\utl>perl -d:ptkdb repath.pl No DB::DB routine defined at d:/perl58m/lib/Devel/ptkdb.pm line 98. BEGIN failed--compilation aborted at d:/perl58m/lib/Devel/ptkdb.pm lin +e 98. Compilation failed in require. BEGIN failed--compilation aborted.
Line 98 of that file is innocent: it just contains following:
use vars qw($VERSION @dbline %dbline);
Has anyone faced similar problem? Could you please share your experience?

That version of ptkdb worked okay with 5.6.1

Courage, the Cowardly Dog.


In reply to How ptkdb could be made to work with perl-5.8.0+Tk-800.024? by Courage

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.