Hello, this test case leads to a segmentation fault: config A tristate "A" if m config MODULES boolean "MODULES" option modules As you can see, the MODULES symbol with the option modules is declared after the first occurrence of an 'm' dependency. (Actually you can drop the MODULES section or use a different symbol name. It does not matter.) Internally 'm' gets converted into (symbol_mod && modules_sym), which adds a dependency on a bad symbol, finally leading to dereferencing a null pointer. If you move the declaration of the MODULES symbol to the top, everything works fine. The crash has been introduced last month with > 6902dccfda005fa4c42410fa064fdd331ab42479 > kconfig: do not special-case 'MODULES' symbol However, things were probably broken before. The problem has only become visible. The reason that configuring a Linux kernel does not crash the configuration system is that there is currently no architecture that has a symbol with a dependency on 'm' anywhere before the MODULES symbol. Regards Martin Walch -- -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
