Description of problem: The environment variables set by the "debugmode" package are not exported (at least in bash), so the only processes that receive the benefits of debug mode are interactive shells. The variables should be exported. Version-Release number of selected component (if applicable): debugmode-9.02.2-1.x86_64 How reproducible: Always Steps to Reproduce: 1. Make sure the "debugmode" package is installed and enabled. 2. env | grep -e MALLOC_ -e G_SLICE Actual results: No output. Expected results (example): MALLOC_CHECK_=1 G_SLICE=debug-blocks MALLOC_PERTURB_=141
Created attachment 412323 [details] export environment variables in debugmode /etc/profile.d/debug.sh: export all non-comment lines instead of sourcing /etc/sysconfig/debug
Gah, more sed mess. Maybe the design should be fixed first (I entered bug 590063).
Cheesier-but-more-efficient fix committed as http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=deb0df0124fbe9b645755a0a44c7cb8044f24719 (debug.csh was set up to handle this already.) Will be in 9.13-1, backported to F-12 and F-13 branches for future updates.
initscripts-9.12.1-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/initscripts-9.12.1-1.fc13
initscripts-9.12.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update initscripts'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/initscripts-9.12.1-1.fc13
initscripts-9.12.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.