Re: [Sisuite-devel] si_monitortk segmentation fault

[Bernard Li]

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, 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 occurs (just set
  core file size to unlimited `ulimit -c unlimited`), and try to analyze
  the core dump with gdb... but I'm quite sure that an update of perl-tk
  will strongly reduce your segfaults...
 
  Okay I have set coredump to unlimited, I'll see if I get a coredump next
  time.
 
  I notice that if I leave si_monitortk running overnight, segfault
  happens...  I'll see if this is reproducible.

 Bernard, instead of generating a core dump, try to run si_monitortk with
 the perl debugger. Example:

 $ sudo perl -dw /usr/sbin/si_monitortk

 Loading DB routines from perl5db.pl version 1.28
 Editor support available.

 Enter h or `h h' for help, or `man perldebug' for more help.

 Tk::MyHList::(/usr/sbin/si_monitortk:15):
 15: @Tk::MyHList::ISA = qw(Tk::HList);
   DB1 r

 If a SEGFAULT occurs you should be able to see in the console the piece
 of code that generated the fault and/or the stack trace (using T).

 -Andrea


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

[Sisuite-devel] si_monitortk segmentation fault

[Bernard Li]

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/systemimager/si_monitor.log is always empty), but perhaps we
should starting doing it to help troubleshoot problems?

I am running strace with si_monitortk right now, but it doesn't look
like it is going to crash, it is somewhat intermittent and hard to
predict when it will crash :(

Thanks,

Bernard

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel