I only now noticed that the error appears within an eval, executed during BEGIN. Maybe it would be a good idea to locate that eval block and see what gets evaluated here...