Is this bug caused by mistaken scalar reference in the command line?

---------
$ mhonarc -add -rcfile [EMAIL PROTECTED]/mail.mrc -outdir
[EMAIL PROTECTED]/www/mail
This is MHonArc v2.5.11, Perl 5.00404 linux
Processing stopped, signal caught: SIGSEGV
---------
---------
$ perl -d /usr/bin/mhonarc -add -rcfile
[EMAIL PROTECTED]/mail.mrc -outdir
[EMAIL PROTECTED]/www/mail

Loading DB routines from perl5db.pl version 1.01
Emacs support available.

Enter h or `h h' for help.

main::(/usr/bin/mhonarc:37):
37:         unshift(@INC, 'lib');       # Should I leave this line in?
  DB<1> c
This is MHonArc v2.5.11, Perl 5.00404 linux
Attempt to free unreferenced scalar at
/home/mhonarc/src/MHonArc2.5.11/release/lib/perl5/site_perl/mhamain.pl line
92, <IN> chunk 1.
        mhonarc::open_archive called at
/home/mhonarc/src/MHonArc2.5.11/release/lib/perl5/site_perl/mhamain.pl line
166
        mhonarc::process_input() called at /usr/bin/mhonarc line 41
DB::fake::(/usr/lib/perl5/perl5db.pl:2083):
2083:     "Debugged program terminated.  Use `q' to quit or `R' to
restart.";
  DB<1> q
$
---------

Thanks,
Rick

---------------------------------------------------------------------
To sign-off this list, send email to [EMAIL PROTECTED] with the
message text UNSUBSCRIBE MHONARC-USERS

Reply via email to