Re: POE sigdies due to die which should never be reached in POE::Queue::Array

Probably just that, although events reference sessions, which pull in  
HEAPs, and who knows what else.  So please send the results to me  
directly.  The list subscribers don't all need to see that.

Thanks again!

-- 
Rocco Caputo - [email protected]


On Jun 24, 2010, at 09:20, Jean Stebens wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> What's that best way of Dumping the queue?
> My best guess: Dumper($_[KERNEL]->[5]);
>
>
> On 06/23/2010 04:21 PM, Rocco Caputo wrote:
>> Can you dump the queue at that point, and send me the results off- 
>> list?
>>
>> -- Rocco Caputo - [email protected]
>>
>>
>> On Jun 21, 2010, at 04:33, Jean Stebens wrote:
>>
>> Hi all,
>>
>> I'm using version 1.2680 of POE.
>>
>> The following exception bumped me the last days:
>>
>> main::on_child_close >> Child has closed its output handles.
>> main::server_stop >> Destroying myself.
>> should never get here... maybe the queue is out of order at
>> /usr/share/perl5/POE/Queue/Array.pm line
>> 202.
>>
>> The main::* functions are my routines beeing called The first one is
>> part of normal flow, the server_stop already tells me that there is
>> something wrong going on - like a DIE Signal - then the DIE reaches  
>> the
>> surface. It seems like POE::Queue::Array has some problems. Were they
>> fixed in any newer versions? I can't find anything about Queue::Array
>> beeing touched over the last year.
>>
>> Cheers.
>> Jean
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iJwEAQECAAYFAkwjW6YACgkQXY+L530SV9H4MwQAo5MM7V7mBD0POrhmzmTRBZV8
> ogUR4PJ0eISGqXoakSPEtlNMBVXxPhzvmPqyZftq/ZwDcxK9IOWXIRwoMecwxliu
> YBKbdvFhaKJqz2Uzg6rDzpJe17WWqJLCx/3+HApwehRsWjQwvnjY1mz1XHFe02rG
> umsRv4PCHljh6Af7uCE=
> =kTEO
> -----END PGP SIGNATURE-----