| commit | 3e5fc80a404a24c858468030b63555cccfb3e79c | |
| author | Dave Airlie <airlied@linux.ie> | |
| Sun, 24 Aug 2008 07:02:26 +0000 (24 17:02 +1000) | ||
| committer | Dave Airlie <airlied@linux.ie> | |
| Sun, 24 Aug 2008 20:35:33 +0000 (25 06:35 +1000) | ||
| tree | 697956db50347ef93490e6220d29b11d9f7f1ee9 | treesnapshot (tar.gz zip) |
| parent | e5b4f19417b75a2d7c1e36934f60a3e836c4337e | commitdiff |
drm: don't set the signal blocker on the master process.
There is a problem with debugging the X server and gdb crashes in
the xkb startup code.
This avoids the problem by allowing the master process to get signals.
It should be safe as the signal blocker is mainly so that you can
Ctrl-Z a 3D application without locking up the whole box. Ctrl-Z the
X server isn't something many people do.
Signed-off-by: Dave Airlie <airlied@redhat.com>
There is a problem with debugging the X server and gdb crashes in
the xkb startup code.
This avoids the problem by allowing the master process to get signals.
It should be safe as the signal blocker is mainly so that you can
Ctrl-Z a 3D application without locking up the whole box. Ctrl-Z the
X server isn't something many people do.
Signed-off-by: Dave Airlie <airlied@redhat.com>
| drivers/gpu/drm/drm_lock.c | diffblobblamehistory |