in reply to Segmentation faults with Net::OPenSSH.pm

Net::OpenSSH is a pure perl module, so a SIGSEGV probably means a bug in the perl interpreter.

Even if you are using an old version of Perl, the module is known to work there, so either you have some custom perl configuration or you are doing something unusual in your code.

Post the output of perl -V and the source for your script. A strace capture may also help and a backtrace obtained with gdb at the point where the exception is raised.

Replies are listed 'Best First'.
Re^2: Segmentation faults with Net::OPenSSH.pm
by Plantir56 (Initiate) on May 19, 2016 at 15:57 UTC
    We narrowed down issue due to stale OpenSSH handles.. basically we create subprocess' inside our modules in different threads and each sub-process in turn creates a new ssh connection... so there could be multiple ssh handles to the same hosts..we were not properly cleaning up the ssh handles.. so when we exit we see SEGV.. cleaning up ssh handles seems to be resolve these to some extent. is this expected with OpenSSH module?
[reply]
      Thread support in Perl 5.8 was quite immature. You are probably triggering some bug there.
[reply]
        Thanks Salva. is doing undef on OpenSSH.pm is the correct way to destroy ssh handle ('undef Net::OpenSSH')
[reply]

In Section Seekers of Perl Wisdom