in reply to perl debug

With which commands did you produce the "errors" in the console? What did you type?

This multiline-output

 <13> ;{ ... looks unusual!

> any advice

Please try reproducing thsi problem by direct debugging from the console with perl -d file.pl and tell us if you still have problems.

I think epic's way to adapt the debugger (in dumpvar_epic.pm ) for it's needs has a conflict with Attribute::Handlers .

If so please report a bug at epic maintainers.

edit

Alternatively at p5p, AFAIR (and for reasons which are beyond my understanding) does dumpvar.pm reside in main. Damian's way to inspect the STASH for subs having an attribute might conflict!

Cheers Rolf

( addicted to the Perl Programming Language)

Replies are listed 'Best First'.
Re^2: perl debug (EPIC vs Attribute::Handlers)
by RamiD (Acolyte) on Jan 22, 2014 at 08:45 UTC

    it's working now

    I don't know what exactly did to make it work but I will write it any way

    some of the steps I found in fourms all over th einternet

    1-)install PathTools

    2-) look for CWD.pm in all perl directory , in my env the CWD.pm is in more than one place , so I did commit the fix in all CWD.pmway

    3-)upgrade Attribute handlers

    4-) maybe we should run per makefile.pl

    and make

    thanks

[reply]
      > I don't know what to add in DB<1>

      type c + RETURN for "continue". The debugger doesn't run automatically.

      type h for help.

      see also perldebug and perldebtut

      > what I did so far is download the Test::Class project and

      > trying to work with it via eclipse,epic

      yeah two things I don't use, sorry.

      I can see from the docs that Test::Class uses attributes, that's all I can say.

      And regarding EPIC ... well you should know that Eclipse is by far not as important in Perl programming as in the Java context.

      I won't install it now to track down the problem ... which ATM looks like a bug for me.

      So if you don't wanna workaround it by replacing either Test::Class or Eclipse, you should post a smallest possible chunk of code to reproduce the problem and hope that someone with a similar work environment can track down the problem.

      If it's positively a bug you should inform the maintainers of EPIC and Test::Class.

      HTH! =)

      Cheers Rolf

      ( addicted to the Perl Programming Language)

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom