ActiveState Community

Breakpoint stopped working in Perl

Posted by fst1 on 2009-10-09 03:47

I am using Komodo IDE 5.1 on winXP - recently breakpoints stopped working - i.e. the debugger does not break in my perl scritps.

I can single-step in the code, and breakpoints is standard modules (e.g. find.pm) do work.

I am running Perl debugging locally.

I guess I somehow have messed up the settings, I have tried to uninstalled and installing Komodo again, this did not solved the problem. A college of mine is running Komodo on same perl scripts with no problems.

Any suggestions on fixing the problem without reinstalling windows ;-)

Best Regards
fst1

ericp | Fri, 2009-10-09 10:16

If you load a main script in Komodo and issue the run command
echo %F
what's the answer? It sounds like there's a character like '&'
that's getting in the way. We try to work with all allowed
characters, but may have overlooked something.

- Eric

toddw | Fri, 2009-10-09 10:44

Also check the breakpoint FAQ that your not hitting a problem there:
http://community.activestate.com/faq/komodo-breakpoints-do-not-work

Cheers,
Todd

fst1 | Mon, 2009-10-12 00:32

I tried the echo %F command, and there has no '&' in the path.

I guessed that to problem was related to the path so I tried moving my script to a local drive. (the script, was originally located on a network drive).

This actually fixed the problem, I don't know why... But in the future I will have this i mind.

Thanks for the help

fst1

ericp | Wed, 2009-10-14 09:24

Breakpoints need to be set in terms of the filenames that
Perl uses. So if you have machine \\foo set to drive h:,
and you load a file as, say, h:\Bar.pm, the breakpoints
won't work, as Perl will think the file is at \\foo\Bar.pm.

It sounds like this was the problem you ran into -- moving
the script to a local drive is one way of solving it, but
loading it via the network would solve it as well.

- Eric