Somebody in the thread at some point said: > 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 #3 is the problem (cannot access memory at address). > I guess I could file a bug if no one else has any suggestions? __ksymtab_strings seems to be a section in vmlinux / z... is it possible that the /boot/vmlinuz-2.6.blah file is unhappy? Or /boot is not mounted, /tmp is full, anything like that? -Andy -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
