Hi Andrea:
Since rebuilding perl-Tk on RHEL4 w/ Perl 5.8.5 (as opposed to the one
built with Perl 5.8.0), I no longer get the segfault. I have checked
the updated perl-Tk RPM into OSCAR trunk.
Thanks,
Bernard
On 4/27/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> Bernard Li wrote:
> >> Moreover
Bernard Li wrote:
>> Moreover, in si_monitor.log are reported only the log messages of the
>> monitoring daemon (si_monitor) and I don't think it's the right place
>> for the log messages of the si_monitortk interface. To debug the problem
>> you could try to generate a core dump when the segfault
Hi Andrea:
I've just had si_monitortk segfault on me again, so I'm replying to
this (old) thread:
On 2/23/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> the main problem is that perl-Tk is quite buggy... :-( have you tried to
> update it to a more recent releaes? I'm using v800.024 without proble
Bernard Li wrote:
> Hi all:
>
> I've had si_monitortk seg fault on me a couple of times already but it
> seems to be getting worse and I would like to get to the bottom of it.
>
> What is the best way to figure out why exactly did it crash?
> Currently I do not think si_monitor logs any messages
Hi all:
I've had si_monitortk seg fault on me a couple of times already but it
seems to be getting worse and I would like to get to the bottom of it.
What is the best way to figure out why exactly did it crash?
Currently I do not think si_monitor logs any messages in log files
(/var/log/systemima
