Red Hat Bugzilla – Bug 263601
'depmod -a' segfaulting
Last modified: 2008-04-25 22:07:15 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run "depmod -a"
2.segfault, almost immediately
This problem started in the past few days. I'm currently running
18.104.22.168-65.fc7, and am up to date (via yum update).
I've run memtest86+ on the system for 16 passes over 12 hours, and it came up
clean. Only depmod is exhibiting the segfault behavior.
I installed the debuginfo version of module-init-tools, and ran it through gdb,
and saw the following:
Starting program: /sbin/depmod -a
Program received signal SIGSEGV, Segmentation fault.
0x0059aee8 in strcmp () from /lib/libc.so.6
#0 0x0059aee8 in strcmp () from /lib/libc.so.6
#1 0x0804ba7c in load_section32 (hdr=0xb1601b8, secname=0x8059c47
conv=0) at moduleops_core.c:18
#2 0x0804c064 in load_symbols32 (module=0xadbfe88) at moduleops_core.c:34
#3 0x0804ae48 in main (argc=2, argv=Cannot access memory at address 0x5aadd37c
) at depmod.c:687
#4 0x00542f70 in __libc_start_main () from /lib/libc.so.6
#5 0x08048ea1 in _start ()
I'm guessing that the 'cannot access memory' is the problem, but I have no clue
Are you still seeing this problem?
no, it went away a while ago.