Bug 176490
| Summary: | segmentation fault line 23:2009 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | raxet <maxer1> |
| Component: | kudzu | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | redhat-bugzilla, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-01-01 07:02:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
raxet
2005-12-23 15:04:32 UTC
*** Bug 176495 has been marked as a duplicate of this bug. *** *** Bug 176491 has been marked as a duplicate of this bug. *** If you run it by hand, does it still segfault? Running in terminal and typing kudzu segfaults. Now it's segfaulting on line 23:2196 after todays update It's not segfaulting in a stock config for me. Can you get a gdb backtrace (preferably with kudzu-debuginfo installed)? When I try a gdb bt on the process I get virtually nothing: Starting program: /usr/sbin/kudzu Reading symbols from shared object read from target memory...(no debugging symbols found)...done. Loaded system supplied DSO at 0x991000 (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x00a11466 in free () from /lib/libc.so.6 So it's glibc-2.3.90-22 that may be the issue.. Is it possible, that this bug is another duplicate of bug #176573 and #176583? Analyzing commands in /etc/rc.d/init.d/kudzu, it seems that the offending line is: kudzu -z || kudzu Tipically I have sometimes the illegal option error, sometimes not, and it happens with the second kudzu command in the line So I tried a two times sequence with: [root fedora ~]# kudzu -z ||gdb kudzu GNU gdb Red Hat Linux (6.3.0.0-1.94rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /sbin/kudzu Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x3b4000 Program exited normally. (gdb) quit [root fedora ~]# kudzu -z ||gdb kudzu GNU gdb Red Hat Linux (6.3.0.0-1.94rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /sbin/kudzu Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x745000 Program received signal SIGILL, Illegal instruction. 0x0805ee2f in run_vm86 () at lrmi.c:733 733 asm volatile ( (gdb) (gdb) quit The program is running. Exit anyway? (y or n) y HIH, Gianluca Gianluca - you've got a different error - that's a LRMI thing. You have 1.2.16-1, correct? raxet: Can you attach your lspci (and lspci -n) output? Fixed in 1.2.17-1. *** This bug has been marked as a duplicate of 176724 *** yes Bill, I have 1.2.16-1. Do I have to open a different bug number? Please do. |