Bug 102617
Summary: | kudzu segfaults | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Chris Ricker <chris.ricker> | ||||||||||||||||
Component: | kudzu | Assignee: | Bill Nottingham <notting> | ||||||||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> | ||||||||||||||||
Severity: | high | Docs Contact: | |||||||||||||||||
Priority: | medium | ||||||||||||||||||
Version: | 1.0 | CC: | diagramsofsuicide, lockhart, mjenner, rvokal | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | All | ||||||||||||||||||
OS: | Linux | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
Fixed In Version: | 1.1.17-1 | Doc Type: | Bug Fix | ||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2003-08-18 21:22:53 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: | |||||||||||||||||||
Attachments: |
|
Description
Chris Ricker
2003-08-18 19:11:06 UTC
Got that strace? Created attachment 93724 [details]
strace -f /usr/sbin/kudzu -t 30 output
Please attach /etc/sysconfig/network-scripts/ifcfg-*. Created attachment 93725 [details]
ifcfg-eth0
Created attachment 93726 [details]
ifcfg-eth1
Created attachment 93727 [details]
ifcfg-lo
Only eth0, eth1, and lo config files. eth1 is disabled in the bios (onboard VIA rhine), but w/o ifcfg-eth1 present, it still segfaults Only thing unusual is that NOZEROCONF is in all the configs, and lo is a file rather than a symlink (symlink stuff is a PITA whenever you upgrade if you've added NOZEROCONF, BTW) Hmm, not related to ifcfg-eth1. I re-enabled that in the bios, and it still segfaults The basic hardware is: [cricker@yoshimi cricker]$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] 00:0b.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) 00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 02) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 70) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If [Radeon 9000] (rev 01) 01:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon 9000] (Secondary) (rev 01) [cricker@yoshimi cricker]$ Created attachment 93728 [details]
lspci -v -v output
*** Bug 102615 has been marked as a duplicate of this bug. *** hardware is probably irrelevant. Can you run MALLOC_CHECK_=2 strace kudzu ..? Is the strace appreciably different? (It's running OK here with those files.) Alternatively, a gdb backtrace would be nice; I'll chuck the debuginfo package on people.redhat.com/notting/kudzu/ Hmm, I did the MALLOC_CHECK_ strace (what's that doing exactly? what its name suggests?). That's a 31 meg strace though, so I'll have to post it on a web server somewhere ;-) I haven't so far managed to get gdb to backtrace. It's not dumping core, and if I just run gdb kudzu, and then try to run it, I get the error: Starting program: /usr/sbin/kudzu 30: No such file or directory. Program exited with code 01. Hmm, FWIW, redhat-config-packages segfaults as well, and it looks like the same cause. Its strace goes: <snip> 4444 open("/etc/sysconfig/network-scripts/ifcfg-eth0", O_RDONLY) = 4 4444 fstat64(4, {st_mode=S_IFREG|0644, st_size=53, ...}) = 0 4444 read(4, "DEVICE=eth0\nBOOTPROTO=dhcp\nONBOO"..., 53) = 53 4444 close(4) = 0 4444 open("/etc/sysconfig/network-scripts/ifcfg-eth1", O_RDONLY) = 4 4444 fstat64(4, {st_mode=S_IFREG|0644, st_size=52, ...}) = 0 4444 read(4, "DEVICE=eth1\nBOOTPROTO=dhcp\nONBOO"..., 52) = 52 4444 close(4) = 0 4444 open("/etc/sysconfig/network-scripts/ifcfg-lo", O_RDONLY) = 4 4444 fstat64(4, {st_mode=S_IFREG|0644, st_size=269, ...}) = 0 4444 read(4, "DEVICE=lo\nIPADDR=127.0.0.1\nNETMA"..., 269) = 269 4444 close(4) = 0 4444 --- SIGSEGV (Segmentation fault) @ 0 (0) --- gdb kudzu set args -t 30 You can't pass args to the program on the gdb commandline. Yes, it's the same segfault. I've made a tweak in CVS so it will (hopefully) stop crashing things like r-c-p and r-c-xfree86, but I still need to track down the bug. Ah, thanks. Now I've got a backtrace: Program received signal SIGSEGV, Segmentation fault. matchNetDevices (devlist=0x95120b8) at kudzu.c:1119 1119 tmpdev = netdevs->next; (gdb) bt #0 matchNetDevices (devlist=0x95120b8) at kudzu.c:1119 #1 0x0805214a in probeDevices (probeClass=CLASS_UNSPEC, probeBus=BUS_DDC, probeFlags=1) at kudzu.c:702 #2 0x0804ac14 in Xconfig (dev=0x9524420) at hwconf.c:123 #3 0x0804d4f2 in configure (dev=0x9524420) at hwconf.c:902 #4 0x0804f197 in configMenu (oldDevs=0x95230a0, newDevs=0x9524420, runFirst=0) at hwconf.c:1750 #5 0x0804ff55 in main (argc=-268374161, argv=0xf000ef6f) at hwconf.c:1956 (gdb) quit On the screen, it was asking if I wanted to configure my newly detected video card (ATI Radeon 9K series) Created attachment 93731 [details]
strace with malloc check
If it will be useful, I've also attached the strace done with MALLOC_CHECK_=2.
This is only 28k bzip2'ed, so it should be small enough for bugzilla. If not,
and you need it, let me know and I'll put it on a web server somewhere.
Created attachment 93732 [details]
malloc_check strace
Oops, attached as text instead of binary. Fixed.
Fixed in 1.1.17-1. Blarg. Change the 'do {} while' loop to 'while {}'. *** Bug 102671 has been marked as a duplicate of this bug. *** *** Bug 102699 has been marked as a duplicate of this bug. *** *** Bug 114676 has been marked as a duplicate of this bug. *** |