Re: Problems on AMD64 with Glib module



On Fri, Jan 09, 2004 at 02:01:39PM -0500, muppet wrote:

Jacek Konieczny said:
On Fri, Jan 09, 2004 at 12:51:58PM -0500, muppet wrote:
from your error message, it sounds like the version of perl you are using is
trying to interpret the file descriptor as a reference.  is it really a
reference, or is it an integer?

It seems it is undef.
...

$VAR1 = [
          undef,
          bless( do{\(my $o = 1)}, 'Glib::IOCondition' )
        ];

oi, that's not good.  what version of Perl are you using?

This is perl, v5.8.2 built for amd64-pld-linux-thread-multi
  Compile-time options: MULTIPLICITY USE_ITHREADS USE_64_BIT_INT
USE_64_BIT_ALL USE_LARGE_FILES PERL_IMPLICIT_CONTEXT

that test  exercises the log message stuff, and therefore counts warnings,
and you're probably getting extra ones.  if you would be so kind, please
run that test directly (as above) and post its output.

[snip output from t/9.t]

sorry, i meant t/a.t .

$ perl -I blib/lib -I blib/arch t/a.t
1..8
ok 1 - in __WARN__: Message **: whee message at t/a.t line 20.
#
ok 2 - in __WARN__: Message **: whee message at t/a.t line 20.
#
ok 3 - in __WARN__: CRITICAL **: whee critical at t/a.t line 22.
#
ok 4 - in __WARN__: CRITICAL **: whee critical at t/a.t line 22.
#
ok 5 - in __WARN__: WARNING **: whee warning at t/a.t line 23.
#
ok 6 - in __WARN__: WARNING **: whee warning at t/a.t line 23.
#
ok 7 - in custom handler message
ok 8 - in custom handler message
ok 9 - in custom handler critical
ok 10 - in custom handler critical
ok 11 - in custom handler warning
ok 12 - in custom handler warning
ok 13 - attempting to connect a non-existant signal
ok 14 - should warn
ok 15 - should warn
# Looks like you planned 8 tests but ran 7 extra.

Greets,
        Jacek



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]