Public bug reported:
I upgraded to edgy a couple of days ago, and on one of my machines, apt-
get is unable to configure linux-restricted-modules due to a segfault in
executing depmod -a -F "System.map-2.6.17-10-generic" "2.6.17-generic".
Can't say why it's acting like that, anyway I recompiled module-init-
tools with debugging symbols and obtained the following:
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) run -a -q -F /boot/System.map-"2.6.17-10-generic" "2.6.17-10-generic"
Starting program: /sbin/depmod -a -q -F /boot/System.map-"2.6.17-10-generic"
"2.6.17-10-generic"
Program received signal SIGSEGV, Segmentation fault.
0x0804a1e4 in main (argc=6, argv=0xbfca9fd4) at ../depmod.c:151
151 ptr = strchr(line, '\n');
(gdb) thread apply all bt
(gdb)
(gdb) backtrace
#0 0x0804a1e4 in main (argc=6, argv=0xbfca9fd4) at ../depmod.c:151
Hope it helps.
** Affects: module-init-tools (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Summary changed:
- After dist-upgrading to edgy, segfault in configuring linux-restricted modules
+ segfault in configuring linux-restricted modules
--
segfault in configuring linux-restricted modules
https://launchpad.net/bugs/67763
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
