----- Original Message ----- From: "Kate L Pugh" kake@earth.li To: "Discussion of development on the OpenGuides software" openguides-dev@openguides.org Sent: 31 January 2004 01:21 Subject: Re: [OpenGuides-Dev] OpenGuides on Windows?
On Fri 30 Jan 2004, IvorW ivorw-openguides@xemaps.com wrote:
677: CORE::open ($fh, "+<&=$fd") or croak (__PACKAGE__ . "::_open_multi_m ap() - unable to open file descriptor for locking: $!");
What does it print when you run it outside the debugger?
Took some persuasion and a cygwin shell:
Search::InvertedIndex::DB::DB_File_SplitHash::_open_multi_map() - unable to open file descriptor for locking: Invalid argument at blib/lib/Search/InvertedIndex.pm line 282 (in cleanup) Class::NamedParms::get() - Attempted to retrieve an undeclared or unitialized named parameter: '-hash' Class::NamedParms::get('Search::InvertedIndex::DB::DB_File_SplitHash=HASH(0x177529c)', '-hash') called at blib/lib/Search/InvertedIndex/DB/DB_File_SplitHash.pm line 373 Search::InvertedIndex::DB::DB_File_SplitHash::close('Search::InvertedIndex::DB::DB_File_SplitHash=HASH(0x177529c)') called at blib/lib/Search/InvertedIndex.pm line 1346 Search::InvertedIndex::close('Search::InvertedIndex=HASH(0x24d56d0)') called at blib/lib/Search/InvertedIndex.pm line 1367 Search::InvertedIndex::DESTROY('Search::InvertedIndex=HASH(0x24d56d0)') called at t/010_update.t line 0 eval {...} called at t/010_update.t line 0 (in cleanup) Class::NamedParms::get() - Attempted to retrieve an undeclared or unitialized named parameter: '-hash' Class::NamedParms::get('Search::InvertedIndex::DB::DB_File_SplitHash=HASH(0x177529c)', '-hash') called at blib/lib/Search/InvertedIndex/DB/DB_File_SplitHash.pm line 373 Search::InvertedIndex::DB::DB_File_SplitHash::close('Search::InvertedIndex::DB::DB_File_SplitHash=HASH(0x177529c)') called at blib/lib/Search/InvertedIndex/DB/DB_File_SplitHash.pm line 395 Search::InvertedIndex::DB::DB_File_SplitHash::DESTROY('Search::InvertedIndex::DB::DB_File_SplitHash=HASH(0x177529c)') called at t/010_update.t line 0 eval {...} called at t/010_update.t line 0 # Looks like your test died before it could output anything.
Hope this helps,
Ivor.