jeremy_r wrote on Mon Jul 9 21:35:12 MEST 2007:
When I run a script in EPIC, I get strange errors that I don't get when running via the command line. For example: Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately after start byte 0xc3) in substitution iterator at /System/Library/Perl/5.8.6/Carp/Heavy.pm line 61,
line 1. Malformed UTF-8 character (unexpected continuation byte 0xa0, with no preceding start byte) in substitution iterator at /System/Library/Perl/5.8.6/Carp/Heavy.pm line 61, line 1. I'm running EPIC 0.6.4 on Mac OS. Any idea what would cause this? thanks
jploski wrote on Mon Jul 9 22:40:44 MEST 2007:
Only two things that might differ in EPIC compared to command line execution come to mind: 1) command line 2) environment variables You can find out what EPIC is using by enabling the debugger console in preferences. With that setting, these pieces of information will be logged to $WORKSPACE/.metadata/.log when you start the script. BTW, you should probably upgrade to 0.6.11 (especially if you use the debugger).
jeremy_r wrote on Tue Jul 10 00:14:56 MEST 2007:
In the debug config, Eclipse is set to use the "native" evironment. I don't currently have any additional variables defined. I'll try upgrading EPIC. I'm using it via EasyEclipse and not sure if it supports updating. thanks
jploski wrote on Tue Jul 10 00:23:26 MEST 2007:
Even if you don't add environment variables yourself, it would still make sense to compare the environment within Eclipse with that on the command line. Upgrading EPIC in EasyEclipse should work ok.
jeremy_r wrote on Tue Jul 10 01:58:53 MEST 2007:
I followed your instructions. I'm running 0.6.11 now. There was a difference in PATH values. I used the PATH value from the CLI in Eclipse and I still get tons of errors. The errors happen when I use the SOAP::Lite module. Not sure if that is significant. Do you have any other ideas?
Note: The above is an archived snapshot of a forum thread. Use the original thread at sf.net to post comments.