Bug 263601 - 'depmod -a' segfaulting
'depmod -a' segfaulting
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: module-init-tools (Show other bugs)
7
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Jon Masters
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-29 11:02 EDT by Lonni J Friedman
Modified: 2008-04-25 22:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-25 22:07:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lonni J Friedman 2007-08-29 11:02:57 EDT
Description of problem:


Version-Release number of selected component (if applicable):
3.3-0.pre11.1.0.fc7.i386

How reproducible:
Every time

Steps to Reproduce:
1.Run "depmod -a"
2.segfault, almost immediately
3.
  
Actual results:
Seg fault

Expected results:
No segfault

Additional info:
This problem started in the past few days.  I'm currently running
2.6.22.4-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:

(gdb) run
Starting program: /sbin/depmod -a

Program received signal SIGSEGV, Segmentation fault.
0x0059aee8 in strcmp () from /lib/libc.so.6
(gdb) bt
#0  0x0059aee8 in strcmp () from /lib/libc.so.6
#1  0x0804ba7c in load_section32 (hdr=0xb1601b8, secname=0x8059c47
"__ksymtab_strings", size=0xbf9510e8,
   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
why.  Help?!
Comment 1 Jon Masters 2008-04-25 21:59:25 EDT
Are you still seeing this problem?
Comment 2 Lonni J Friedman 2008-04-25 22:07:15 EDT
no, it went away a while ago.

Note You need to log in before you can comment on or make changes to this bug.