gdb is among the list of packages that often cause a stall in OBS - OBS detects
this after a while and cancels the build.

The issue though is that unreliable builds are a pain and must not happen
(especially when being a ring package; it is built very often in the stagings
and every fail requires the staging managers to interact)

The current fail I have here stops with:

<[ 6299s] Running target unix/-m32/-fPIC/-pie
>[ 6299s] Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
>[ 6299s] Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
>[ 6299s] Using /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
>[ 6299s] Running /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/gdb.xml/tdesc-arch.exp ...
>[ 6299s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version  7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory 
>[ 6299s] 
>[ 6299s] 
>[ 6299s] 		=== gdb Summary ===
>[ 6299s] 
>[ 6299s] # of expected passes		8
>[ 6300s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version  7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory 
>[ 6300s] 
>[35104s] ### WATCHDOG MARKER END ###
>[35104s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl)
>[35104s] or the build host has a kernel or hardware problem...
>
>
>Job seems to be stuck here, killed. (after 28800 seconds of inactivity)