I understand the difficulty in trying to troubleshoot a script with just the snippet. That is why I am here.
The problem is that it is a little of 6000 lines of code with a dependency on an external application and only fails on a subset of the systems that run the tool. I can not actually get the code to fail on my system, but some of the user's systems fail pretty reliably and always on the fileno command.
I was mostly looking for any insight anyone might have into what fileno does internally on a Win32 system that might cause the process termination, or even more generally if there is a way to tell what caused perl to jump to it's end blocks. I am just not familiar enough with the perl source code to follow fileno all the way down to it's actual implementation. And I was not aware if there were any status variables that might indicate what caused the jump to the end blocks.
Perl is not executing the line of code after the fileno command, and it not throwing an exception. It simply jumps to the cleanup.
In reply to Re^2: Perl jumps to END logic after fileno (Win32)
by dchidelf
in thread Perl jumps to END logic after fileno (Win32)
by dchidelf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |