RE: Health monitor of a multi-threaded process

> >     4) Threads are not in any infinite loop.

> This requires solving the Halting Problem.  If your management is
> demanding this
> feature, I suggest informing them that it is mathematically impossible.

Christ, these academics! They take real world problems that engineers
actually *solve* every day and then "prove" they're impossible.

Actually, it's trivial to solve this. Just wait. If the thread terminates,
it wasn't in an infinite loop.

If you've got the budget, I believe SGI has a machine that can do an
infinite loop in less than five seconds. That will save a lot of waiting.

DS


-
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/

---

• References:
  • Re: Health monitor of a multi-threaded process
    • From: Chris Snook <[email protected]>

• Prev by Date: Re: [rfc][patch] dynamic data structure switching
• Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Previous by thread: Re: Health monitor of a multi-threaded process
• Next by thread: [PATCH] m68k(nommu): Add missing syscalls
• Index(es):
  • Date
  • Thread

[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]