[NETFRAME] Net::Packet::Dump / Net::Frame::Dump::Online - Concurrent Simultaneous Capture Limit?

[GomoR]

On Thu, Jun 11, 2009 at 10:32:08AM -0400, Darien Kindlund wrote:
> On a related note, it seems that Net::Frame::Dump::Online->stop()
> seems to indirectly trigger any END {} blocks within the parent
> process.  Let me explain by example:
[..]
> If you run the following code, you'll see that the "END CALLED!"
> message appears after the $dump->stop call (which is unexpected) as
> well as at the end of the script (which is expected).  I was thinking
> about using the isFather and isSon functions to distinguish which
> process we're in; however, it seems that these functions report back
> the same information in both END calls (which is odd).  Any thoughts?

You are completely right. Nice catch, I fixed the bug in 
Net::Frame::Dump 1.06 release currently uploading to CPAN.

Regards,

-- 
  ^  ___  ___             http://www.GomoR.org/          <-+
  | / __ |__/               Research Engineer              |
  | \__/ |  \     ---[ zsh$ alias psed='perl -pe ' ]---    |
  +-->  Net::Frame <=> http://search.cpan.org/~gomor/  <---+