Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to free unreferenced scalar during global destruction #4

Open
kiwiroy opened this issue Jan 23, 2017 · 1 comment
Open

Attempt to free unreferenced scalar during global destruction #4

kiwiroy opened this issue Jan 23, 2017 · 1 comment

Comments

@kiwiroy
Copy link

kiwiroy commented Jan 23, 2017

This was raised and reproduced on dbi-users, thanks @ronsavage.

I've written a further test for this which is more simple and passes far less options to connect() to aid in identification of the cause and could possibly be made subject of a pull request.

observations

  • In the monkey patched DBD::CSV::Table::DESTROY uncommenting this stops the warnings.
  • Specifying csv_tables is a sure way to trigger the warning, however I have seen multiple warnings from this code, from the test_with_options() for (1 .. 100); calls, so I doubt this is the full story.
  • The SV that is unreferenced is always the Text::CSV_XS object, so I don't know if the bug lies there - csv_tables is not an option to new() there though.
@Tux
Copy link
Member

Tux commented Jun 26, 2017

@rehsack You promised to have a look. This is just a reminder. See https://github.com/perl5-dbi/DBD-CSV/tree/master/sandbox/issue-4 for test files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants