From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031014 Description of problem: When running "/sbin/modprobe -c" as a normal user (kernel-2.6.0-0.test8.1.63), modprobe segfaults. It runs fine as root. Since the binary is not compiled with debugging symbols, there is not much to be seen in strace or gdb. Version-Release number of selected component (if applicable): modutils-2.4.25-13 How reproducible: Always Steps to Reproduce: 1. Boot 2.6.0-test kernel 2. Log in as normal user 3. run "/sbin/modprobe -c" Actual Results: modprobe segfaults Expected Results: Show the currently used configuration, or show an error message (if the command is meant to be run as root only) Additional info:
This works for me with 2.4.26-2. Please reopen if it persists.
Still segfaults for me. Any pointer to a document explaining how to use the -debuginfo packages to get the debugging symbols back would be highly appreciated. Thanks.
Just install modutils-debuginfo, and run modprobe under gdb.
Created attachment 97335 [details] modprobe backtrace (truncated, goes on line this for ~150 lines total)
OK, things are getting stranger. Running /sbin/modprobe in an xterm or at the console works just fine. Starting a screen and running modprobe in it causes modprobe to segfault. gdb says: (gdb) run -c Starting program: /sbin/modprobe -c Program received signal SIGSEGV, Segmentation fault. 0x080593e5 in gather_options (argv=0xfeeb1e78) at modprobe.c:1098 1098 if (strchr(*argv, ' ')) { The backtrace is... interesting. Attached.
Can you attach your /etc/modprobe.conf and /etc/modprobe.conf.dist?
Created attachment 97338 [details] modprobe.conf
Created attachment 97339 [details] modprobe.conf.dist
Ah, it's screen that's the trigger. Looking at it.
Works now with screen-4.0.2-1 and modutils-2.4.26-14.