Bug 284904 – using debug flag screws up PAM,nano& possibly evdev

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Geoff Madden 2009-09-14 11:00:48 UTC]

login to kde4.3.1 was unable due to a segmentation fault. Took the advice of the crash handler,and recompiled system with the debug flag enabled.Which resulted in excessive module checking by pam-1.1.0,so much so that the system timed out,also not able to login on another terminal screen,same result. While trying to use nano to edit config files,was greeted by similar module checking,with the result that I wasn't able to do any editing,didn't try VI,as it was now 0200. Next evening managed to get a login on a terminal and recompiled pam and nano with the debug flag disabled.some success with this,added sys-libs/pam -debug to /etc/portage/package.use. in the hope that the problem would not reappear,but this doesn't appear to work as I noticed the debug flag was reset when I setup the world recompile.
Regarding evdev the keyboard works ok but I have had to reuse the mouse driver to get it to work in X,instead of evdev.

Reproducible: Always

Actual Results:  
after recompile and mouse reinstated am now able to login and use the system normally. not too sure what caused the segmentation fault originally as it does not appear to be there now.

Expected Results:  
will wait and see what happens after the world recompile.

system is Asus a7v-e 1G ram,Athlon Processor. Kde-4.3.1 portage dated 14-09-2009(this evening)
kept up2date at least weekly

[Comment 1 Patrick Lauer 2009-09-14 11:08:15 UTC]

>Took the advice of the crash handler,and recompiled system with the debug flag enabled.

It was talking about CFLAGS, not USEflags. 

Unconditionally enabling USE="debug" will have these effects, they are a feature and not a bug.

http://www.gentoo.org/proj/en/qa/backtraces.xml might be of interest to you.