On 17 Jan 2006, Lee Revell wrote:
> The problem is, this python application is not supposed to kill
> anything, so I think it is a bug in X, but I cannot find any way to
> trace the fault. Even gdb says the application was killed, so exited
> normally, and results in no back trace.
>
> Is there any way in Linux to find out who did the "killing" ?"
It's probably easiest to build the X server with debugging and use the
two-machine procedure outlined in
<http://xorg.freedesktop.org/wiki/DebuggingTheXserver>.
(If you don't have two machines and two displays, debugging it gets
very much harder.)
--
`Logic and human nature don't seem to mix very well,
unfortunately.' --- Velvet Wood
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
