DBD::CSV attempt to free unreferenced scalar during global destruction

2017-01-16 Thread Roy Storey
Hello, I'm here looking for help with an issue I'm having with DBD::CSV. Specifically, I'm attempting to use the 'after_parse' callback to handle a csv file with a data defined variable number of columns and hit a warning on an attempt to free unreferenced scalar during global destruction. I've

Fwd: DBD::CSV attempt to free unreferenced scalar during global destruction

2017-01-16 Thread Roy Storey
Hi Ron, Thanks for taking the time to have a look. I see you are using 5.20.2, could it be that your installed modules are not at the same version as mine? Sorry for not being more detailed in my report. I've updated the 'cpanfile' to lock to specific versions I'm using and removed the

Re: DBD::CSV attempt to free unreferenced scalar during global destruction

2017-01-16 Thread Ron Savage
Hi Roy I ran your code - unsuccessfully - and added the output as a comment to your gist. On 16/01/17 20:54, Roy Storey wrote: Hello, I'm here looking for help with an issue I'm having with DBD::CSV. Specifically, I'm attempting to use the 'after_parse' callback to handle a csv file with

Re: Fwd: DBD::CSV attempt to free unreferenced scalar during global destruction

2017-01-16 Thread Ron Savage
Hi Roy See updated gist for re-run and module versions. And, I'm on the list, so no need to copy me directly. On 17/01/17 10:09, Roy Storey wrote: Hi Ron, Thanks for taking the time to have a look. I see you are using 5.20.2, could it be that your installed modules are not at the same

Re: Fwd: DBD::CSV attempt to free unreferenced scalar during global destruction

2017-01-16 Thread Roy Storey
On 17 January 2017 at 13:12, Ron Savage wrote: > Hi Roy > > See updated gist for re-run and module versions. > Ok, so the warning is reproducible. > And, I'm on the list, so no need to copy me directly. Sorry my bad, or gmail's bad, but most likely mine. > > > On