This new version of the patch fixes issues in the first version and adds many more logging paths that needed fixing.
The cause of a bug that was thought to be fixed by this patch has been found. As such, the only known effect of this patch is to not crash valgrind when attempting to log in a signal handler. Since this is a large patch to be adding this late in the cycle, I am marking this bug as won't fix for precise. We can add it in Q. ** Patch added: "Proposed fix for signal-unsafe logging v2" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+attachment/3036000/+files/228_sigsafe_logging.patch ** Also affects: xorg-server (Ubuntu Precise) Importance: Medium Assignee: Chase Douglas (chasedouglas) Status: In Progress ** Also affects: xorg-server (Ubuntu Q-series) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Precise) Status: In Progress => Won't Fix ** Changed in: xorg-server (Ubuntu Q-series) Status: New => Triaged ** Changed in: xorg-server (Ubuntu Q-series) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Q-series) Assignee: (unassigned) => Chase Douglas (chasedouglas) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
