Re: Problem with PDFLIB barcode generation

Hi

Can you minimise the code sample so that monks can just attack the issue you are facing ?
Your code above is not readily executable on my m/c and when i try to install PDFLIB cannot be installed without pdflif9 software.
Are you sure this is not just a relative paths issue
I hope you are aware of perl debug found in perldoc perldebtut or perldebug.

run your program in perl -d program.pl (type h for command menu)
set a breakpoint at line no. 44 in the case of this script using the command $>b 44
continye execution upto break using command $>c
step into the set_option method and see why its dieing

If you make your code sample compact, it will be better i feel
update a suggestion try even placing the missing file in current directory . I see you are using "." for determining current directory. check FindBin and determine your script path using $FindBin::Bin .

The temporal difficulty with perl is u need to know C well to know the awesome.else u just keep *using* it and writing inefficient code

Comment on Re: Problem with PDFLIB barcode generation

Replies are listed 'Best First'.
Re^2: Problem with PDFLIB barcode generation by sriram_perl_diver (Novice) on Nov 06, 2014 at 05:21 UTC
Thanks for the reply perlron I posted the specific code above in another reply. Many thanks for introducing the debugging steps. I'm a perl beginner and was completely unaware about this. Surely I'll use this debugging and will try to figure out what could be the issue stopping my code. I fixed the missing file issue by placing it in my current directory. The problem with the pdflib.upr was fixed by then. Now I'm getting an exception, which doesn't get written out to the logfile or console. Thanks	[reply]
Re^3: Problem with PDFLIB barcode generation by perlron (Pilgrim) on Nov 06, 2014 at 10:21 UTC
Thats great news. Try using the capture method in module Capture::Tiny to capture errors and print it , if you feel the control is going outside the perl script. (pdflib9 might be causing an issue externally). FYI your error message(if any) from perl command execution will be stored in $! variable which u can print. The temporal difficulty with perl is u need to know C well to know the awesome.else u just keep using* it and writing inefficient code*	[reply]