Xorg spews glibc internal abort trace to controlling terminal where I cannot capture it
Bug #345748 reported by
Kees Cook
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xorg-server (Ubuntu) |
Fix Released
|
Medium
|
Bryce Harrington | ||
Bug Description
When Xorg is aborted by an internal glibc failure (memory corruption, buffer checks, etc), the trace message goes to vt7 rather than stderr where it can be recorded in gdm logs. Attached patch requests glibc to write those messages to stderr instead.
Related branches
Revision history for this message
| Kees Cook (kees) wrote | #2 |
| Changed in xorg-server (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in xorg-server (Ubuntu): | |
| assignee: | nobody → bryceharrington |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in xorg-server: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package xorg-server - 2:1.6.0-0ubuntu4
---------------
xorg-server (2:1.6.0-0ubuntu4) jaunty; urgency=low
* Add 168_glibc_
- Catch glibc internal abort traces on stderr instead of to the
controlling terminal (LP: #345748).
-- Kees Cook <email address hidden> Thu, 19 Mar 2009 22:39:33 -0700