Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7509889
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T23:03:45+00:00 2026-05-29T23:03:45+00:00

I found a bug in the Perl module IO::Socket::SSL and I could probably fix

  • 0

I found a bug in the Perl module IO::Socket::SSL and I could probably fix it, however, I’m concerned about testing the fix. I downloaded the source package from Debian (as my intend is to produce a Debian package or a patch for that) and looked at the t/ directory. There, I found the test coverage is scarce at best.

So I’d like to ask if there is a well known procedure for testing this code. Is there another test (not in the distribution) with better coverage? Also, I would like to use testing modules not in the core distribution (Test::LeakTrace) for testing. Would that be OK?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T23:03:46+00:00Added an answer on May 29, 2026 at 11:03 pm

    A quick CPAN search indicates that IO::Socket::SSL is on CPAN. Furthermore, corelist (http://perldoc.perl.org/corelist.html) as of 5.14.1 doesn’t report knowing about it, so it is not distributed with core Perl. So, to your questions.

    First, CPAN tells me that Steffen Ullrich is still the author and maintainer of the module and although the documentation states a copyright as of 2005, his latest CPAN release is as of 2011. If you’re not using Debian Sid, there is a decent chance that he has fixed your problem but it has not yet been repackaged for Debian. Before you do anything, you should try to get a hold of the latest sources. You can do this by downloading a copy of the tarball from CPAN. (Many modules maintain source control on GitHub and there may be more recent developments than the CPAN tarball, but Steffen has not told us where to find them, so we’ll just have to start there.) The full test suite should be in this tarball.

    The procedure, which you probably know, is to first build the source:

    perl Makefile.PL
    make
    

    then running the test suite:

    make test
    

    If the tests do not cover what you need, you should update the tests and email Steffen (his email and a website are available on the author’s page). He will likely have ideas for how to best supply a patch with tests.

    I believe that CPAN is there and should be used, so if it were up to me, I would say that you should use Test::LeakTrace and specify it as a build dependency. However, Steffen may feel differently, so you should talk with him about it.

    Hope that helps! Good luck!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

What if I think, that I found a bug in an open-source-app? What steps
I found a possible bug in perl's closures and $1 regexp variables. Simply, they
I found a bug in the Contains statement in Linq (not sure if it
I found strange bug (maybe). When I send parameters to $.ajax in a form
Say I just found a bug involving javascript workflow in a web app. Most
I just found a bug in my Rails app which would lead to certain
We've found a bug in old code where connections aren't being closed. It's an
I just found a bug in one of the rake tasks shipped with Rails.
I am working on this yahoo pipe Regex and I found a bug I'm
I found an interesting bug in a program that I implemented somewhat lazily, and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.