On Wed, Jan 19, 2000 at 09:18:56PM +0100, [EMAIL PROTECTED] wrote:
> Just to become familiar with the debug feature before I use it in the real code I
>wrote a simple
> test
> script. I recognized the following: if I use unloop() to stop the loop, the watcher
>counter does
> not
> change. If I u
Just to become familiar with the debug feature before I use it in the real code I
wrote a simple
test
script. I recognized the following: if I use unloop() to stop the loop, the watcher
counter does
not
change. If I use the cancel phrase (as I send it with this message), there is a point
when a
> Huh? _memory_counters() returns an array. You can formatted it as well
> or badly as you like. :-)
O, hm! Indeed ... sorry! I built it so quickly into a warn() statement that I missed
that format point ...
> This little event feature is just a stop gap.
Ok.
Jochen
On Wed, Jan 19, 2000 at 07:32:48PM +0100, [EMAIL PROTECTED] wrote:
> > Perhaps you can do something like this:
> >
> > Event->timer(interval => 2, cb => sub {
> > warn 'Event memory: ' . join ' ', Event::_memory_counters()
> > });
>
> I see. I took my first steps and recognized the format
> Perhaps you can do something like this:
>
> Event->timer(interval => 2, cb => sub {
> warn 'Event memory: ' . join ' ', Event::_memory_counters()
> });
I see. I took my first steps and recognized the format:
2000
So, there are two watchers of type 4. Unfortunately, I'm
On Wed, Jan 19, 2000 at 07:09:02PM +0100, [EMAIL PROTECTED] wrote:
> So, I saw the patch included the free() checking code as well, so I will now start
>to instruct my
> application to run with Events debugging feature. I will report the results.
>
> _memory_counters() replies the number of watc
Hello,
> I'll use a different #define ...
> EVENT_MEMORY_DEBUG. Attached is a patch vs. 0.58. Can you add
> -DEVENT_MEMORY_DEBUG to the Makefile and try again?
Well, this works! I applied your patch, and the new Event.pm (build with
-DEVENT_MEMORY_DEBUG)
passed all tests successfully even wit
On Wed, Jan 19, 2000 at 05:25:35PM +0100, [EMAIL PROTECTED] wrote:
> O, hm, by the way, I see this is a threaded perl (which you do not suggest) ... but
>can this
> really cause such problem? I'll see if I found another installation without
>threading ...
As long as you don't use threads, it sh
On Wed, Jan 19, 2000 at 05:33:20PM +0100, [EMAIL PROTECTED] wrote:
> > > "Reference miscount in sv_replace() at blib/lib/Event.pm line 184."
> >
> > Whoa! I've never seen that. Can you post the output from 'perl -V'?
> > Maybe I can try to reproduce the problem with exactly the same version
> >
On 19 Jan, [EMAIL PROTECTED] wrote:
> perl -V reported that my perl was not compiled for debugging, so I set DEBUGGING in
> Makefile.PL by adding "DEFINE => '-DDEBUGGING'". Sorry, I'm not that familiar with
> MakeMaker, but a look through the docs and a check of the resulting makefile made me
> th
10 matches
Mail list logo
