It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,788

question asked: Jun 24 '09, 10:17 p.m.
question was seen: 8,842 times
last updated: Jun 24 '09, 10:17 p.m.

Related questions

FAQ - How this Forum works

Using cqperl

0
Andrew DeFaria (161●1●5●1) | asked Jun 24 '09, 10:17 p.m.
I've installed EPIC (Perl Plugins) to RTC. I've set it up to run and debug regular Perl stuff but a lot of my work involves using cqperl. How do I run and debug things using cqperl.

When I set the Perl Executable in the Perl EPIC section of Windows: Preferences to C:\Program Files\Rational\Clearquest\cqperl.exe and attempt to run or debug a cqperl script I get: 

An internal error occurred during: "Launching testOpen.pl".

java.lan.NullPointException

6 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Andrew DeFaria (161●1●5●1) | answered Jun 28 '09, 12:40 a.m.
Anybody???
0
permanent link
Johannes Rieken (1.2k●1) | answered Jun 29 '09, 3:44 a.m.
defaria wrote:
I've installed EPIC (Perl Plugins) to RTC. I've set it up to run and
debug regular Perl stuff but a lot of my work involves using cqperl.
How do I run and debug things using cqperl.

When I set the Perl Executable in the Perl EPIC section of Windows:
Preferences to C:\Program Files\Rational\Clearquest\cqperl.exe and
attempt to run or debug a cqperl script I get:

An internal error occurred during:
"Launching testOpen.pl".
java.lan.NullPointException


Please post a full stack trace so we can figure out where the problem is
rooted. However, it is possible that this is a defect in the EPIC
plugins and unrelated to RTC.


--
Cheers, Johannes
Agile Planning Team
0
permanent link
Andrew DeFaria (161●1●5●1) | answered Jun 29 '09, 10:44 a.m.

Please post a full stack trace so we can figure out where the problem is
rooted.


How do I do that? IIRC this was all I saw.

However, it is possible that this is a defect in the EPIC plugins and unrelated to RTC.


What then is the solution for a person who needs to write and debug cqperl oriented stuff? Or are you saying that such people are are just out of luck?

Why would debugging work regular Perl but now cqperl? My guess: Because cqperl is a script and not a binary...
0
permanent link
Johannes Rieken (1.2k●1) | answered Jun 30 '09, 8:46 a.m.
defaria wrote:
zrlrkewrote:

Please post a full stack trace so we can figure out where the
problem is
rooted.

How do I do that? IIRC this was all I saw.

However, it is possible that this is a defect in the EPIC plugins
and unrelated to RTC.

What then is the solution for a person who needs to write and debug
cqperl oriented stuff? Or are you saying that such people are are
just out of luck?


Of course not. It's just another bug tracker. Epic related tickets are
managed here:
http://sourceforge.net/tracker/?atid=545274&group_id=75859&func=browse



--
Cheers, Johannes
Agile Planning Team
0
permanent link
Andrew DeFaria (161●1●5●1) | answered Jun 30 '09, 12:06 p.m.
Well I first wanted to verify it was indeed a problem. Secondly I was hoping for anybody else who happens to use cqperl and who uses RTC to assist in development and debugging of such scripts to perhaps chime in with at "Yeah that's problem but here's a workaround".

Finally, I highly doubt that EPIC developer will really care about the highly specialized version of Perl called cqperl which is a IBM/Rational product. IOW what would stop the EPIC guys from saying "Use a better version of Perl" or "We don't support cqperl - talk to Rational"?
0
permanent link
Andrew DeFaria (161●1●5●1) | answered Jun 30 '09, 5:54 p.m.
I was able to make some more progress. I changed the Perl executable to point to cqperl.exe and set the Interpreter type back to Standard. Now I can at least step through scripts however when I attempt to use the debugger I get an error stating: 

Error displaying local variables 

Install PadWalker and restart Eclipse or disable display of local variables.


I also see: 

Bareword found where operator expected at D:/Profiles/p6258c/workspace/.metadata/.plugins/org.epic.debug/epic_breakpoints.pm line 49, near "$DB::OUT _abs_path" 

(Missing operator before _abs_path?) 

Default die handler restored.


Trouble is I don't have PadWalker nor do I have ppm with which to install it. As you may know IBM/Rational's ccperl is an ActiveState based, specialize Perl and they not give you tools to install additional Perl CPAN modules into cqperl.

Is there a way to get ppm and PadWalker to install into this beast or am i just out of luck?

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.