wsod: Fixed gdb hangs when generating backtraces.

After a long and hard battle with the gods of bugs I finally fixed
this stupid hang. I had to dig into the gdb source code, and gdb the
hell out of gdb, but it's now solved.

First of all, we should call gdb with -batch which exits automatically.
This however is not enough to fix it. The bug was that gdb was haning
while trying to set attributes on stdin because it was waiting for input.
This is obviously problematic when running in non-interactive mode, so
I had to pipe /dev/zero to stdin to fix it.
While at it, I also fixed the piping of stdout and stderr to be nicer.

3 files changed, 6 insertions, 1 deletions

diff --git a/ChangeLog b/ChangeLog
index 86c6cff43..f49d0c8b0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,6 @@
+2013-11-05 Tom Hacohen
+        * wsod: Fixed gdb hangs when generating backtraces.
+
 2013-10-07 Mike Blumenkrantz
 
         * removed "raise on focus" config option
diff --git a/NEWS b/NEWS
index dcb8ec509..d06bd69bd 100644
--- a/NEWS
+++ b/NEWS
@@ -234,3 +234,4 @@ Fixes:
     * fixed bug where new files could not be created repeatedly
     * fixed filemanager spring window closing when dragging from desktop
     * fixed catching XWindow closes during DND operations on those windows
+    * wsod: Fixed gdb hangs when generating backtraces.
diff --git a/src/bin/e_sys_main.c b/src/bin/e_sys_main.c
index b48f1c08b..edbb70da4 100644
--- a/src/bin/e_sys_main.c
+++ b/src/bin/e_sys_main.c
@@ -168,10 +168,11 @@ main(int argc,
 
         snprintf(buffer, 4096,
                  "%s --pid=%i "
+                 "-batch "
                  "-ex 'set logging file %s' "
                  "-ex 'set logging on' "
                  "-ex 'thread apply all backtrace full' "
-                 "-ex detach -ex quit > /dev/null 2> /dev/null",
+                 "-ex detach &> /dev/null < /dev/zero",
                  cmd,
                  pid,
                  output ?: "e-output.txt");