hmm... i'm reflecting your problem, and i can't say i know a solution. but two things come into my mind: first, if you localize hooks for the standard signals, you might get an error message even if perl itself doesn't produce one, e.g.: 
local $SIG{HUP} = $SIG{TRAP} = ... = \&sig_message;
...
sub sig_message {
   my $sig = shift;
   print STDERR "Got signal $sig\n";
}

[download]
the second thought that i have is that one shouldn't always trust berkeley db's. at least with GDBM_File i encountered severe data losses. if you don't like to rely on a sql-database, and the amount of data is manageable you'll possibly better off with using plain files. if you serialize your data hashes via Storable.pm you'll get clear and reproducable results.

In reply to Re: Problem with untie by TOD
in thread Problem with untie by ruzam

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.