PDA

View Full Version : segfault on Fedora 9



StePhAngel06
29th July 2008, 08:31 AM
Hi all,
I am using a software (proprietary) under Fedora 9.
This software perfectly runs under RedHat Linux 8, RedHat 9, and Fedora 8. But I have a problem with Fedora 9.
Every 90 minutes, I have a crash.

This is what I have into /var/log/messages file:

Jul 28 18:06:06 fedora xip[27089]: Lancement du serveur xip
Jul 28 19:36:12 fedora kernel: xip[27096]: segfault at 46 ip 004a8779 sp b7fd6284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 19:36:12 fedora kernel: xip[27096]: segfault at 46 ip 004a8779 sp b7fd6284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 19:36:12 fedora init: tty12 main process (27089) killed by SEGV signal
Jul 28 19:36:12 fedora init: tty12 main process ended, respawning
Jul 28 19:36:12 fedora xip[27193]: Lancement du serveur xip
Jul 28 21:06:18 fedora kernel: xip[27198]: segfault at 46 ip 004a8779 sp b7f5b284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 21:06:18 fedora kernel: xip[27198]: segfault at 46 ip 004a8779 sp b7f5b284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 21:06:18 fedora init: tty12 main process (27193) killed by SEGV signal
Jul 28 21:06:18 fedora init: tty12 main process ended, respawning
Jul 28 21:06:18 fedora xip[27300]: Lancement du serveur xip
Jul 28 22:36:35 fedora kernel: xip[27307]: segfault at 46 ip 004a8779 sp b8070284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 22:36:35 fedora kernel: xip[27307]: segfault at 46 ip 004a8779 sp b8070284 error 4 in libc-2.8.so[46a000+163000]
Jul 28 22:36:35 fedora init: tty12 main process (27300) killed by SEGV signal
Jul 28 22:36:35 fedora init: tty12 main process ended, respawning
Jul 28 22:36:35 fedora xip[27410]: Lancement du serveur xip
Jul 29 00:06:42 fedora kernel: xip[27416]: segfault at 46 ip 004a8779 sp b7f79284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 00:06:42 fedora kernel: xip[27416]: segfault at 46 ip 004a8779 sp b7f79284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 00:06:42 fedora init: tty12 main process (27410) killed by SEGV signal
Jul 29 00:06:42 fedora init: tty12 main process ended, respawning
Jul 29 00:06:42 fedora xip[27521]: Lancement du serveur xip
Jul 29 01:36:48 fedora kernel: xip[27526]: segfault at 46 ip 004a8779 sp b7f3a284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 01:36:48 fedora kernel: xip[27526]: segfault at 46 ip 004a8779 sp b7f3a284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 01:36:48 fedora init: tty12 main process (27521) killed by SEGV signal
Jul 29 01:36:48 fedora init: tty12 main process ended, respawning
Jul 29 01:36:48 fedora xip[27619]: Lancement du serveur xip
Jul 29 03:06:54 fedora kernel: xip[27624]: segfault at 46 ip 004a8779 sp b7f3b284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 03:06:54 fedora kernel: xip[27624]: segfault at 46 ip 004a8779 sp b7f3b284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 03:06:54 fedora init: tty12 main process (27619) killed by SEGV signal
Jul 29 03:06:54 fedora init: tty12 main process ended, respawning
Jul 29 03:06:54 fedora xip[27724]: Lancement du serveur xip
Jul 29 04:37:00 fedora kernel: xip[27729]: segfault at 46 ip 004a8779 sp b80d6284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 04:37:00 fedora kernel: xip[27729]: segfault at 46 ip 004a8779 sp b80d6284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 04:37:00 fedora init: tty12 main process (27724) killed by SEGV signal
Jul 29 04:37:00 fedora init: tty12 main process ended, respawning
Jul 29 04:37:00 fedora xip[27837]: Lancement du serveur xip
Jul 29 06:07:18 fedora kernel: xip[27842]: segfault at 46 ip 004a8779 sp b7f44284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 06:07:18 fedora kernel: xip[27842]: segfault at 46 ip 004a8779 sp b7f44284 error 4 in libc-2.8.so[46a000+163000]
Jul 29 06:07:18 fedora init: tty12 main process (27837) killed by SEGV signal
Jul 29 06:07:18 fedora init: tty12 main process ended, respawning
Jul 29 06:07:18 fedora xip[28569]: Lancement du serveur xip

Can someone help us understanding the problem and helping us in finding a solution to solve it?

Thanks in advance for your help.

Vouters
4th August 2008, 01:34 AM
You ought to have the following, if


$ /sbin/sysctl -a | grep core
kernel.core_uses_pid = 1
kernel.core_pattern = /opt/core


This means that if you have or add in your /etc/rc.d/init.d/xip ( I guess you $ service xip start)


$ ulimit -c unlimited

you will produce a core.$(pid) in /opt directory. If I refer to the last line of your messages log, you ought to obtain a /opt/core.28569 file.
Look at your /etc/rc.d/init.d/xip to locate any xip specific executable and then


$ gdb executable /opt/core.$(pid)

This may or may not give you clues as to what is happening.

Hoping this will help you.
Philippe

Vouters
4th August 2008, 02:33 AM
$ gdb executable /opt/core.$(pid)

may NOT give clues if the program has been compiled without the -g option.

In such case, request from your xip software editor an image built WITH -g option.

Philippe