Re: signals logged / [RFC] log out-of-virtual-memory events

> +	switch(sig) {
> +	case SIGQUIT: 
> +	case SIGILL: 
> +	case SIGTRAP:
> +	case SIGABRT: 
> +	case SIGBUS: 
> +	case SIGFPE:
> +	case SIGSEGV: 
> +	case SIGXCPU: 
> +	case SIGXFSZ:
> +	case SIGSYS: 
> +	case SIGSTKFLT:

Unconditional? That's definitely a very bad idea. If anything only unhandled
signals should be printed this way because some programs use them internally. 
But I think your list is far too long anyways.

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

Follow-Ups:
- Re: signals logged / [RFC] log out-of-virtual-memory events
  - From: Andrea Righi <[email protected]>
- Re: signals logged / [RFC] log out-of-virtual-memory events
  - From: Folkert van Heusden <[email protected]>

References:
- Re: [RFC] log out-of-virtual-memory events
  - From: Rik van Riel <[email protected]>
- Re: signals logged / [RFC] log out-of-virtual-memory events
  - From: Jan Engelhardt <[email protected]>
- Re: signals logged / [RFC] log out-of-virtual-memory events
  - From: Folkert van Heusden <[email protected]>

Prev by Date: Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
Next by Date: Re: [patch 01/10] SLUB: add support for kmem_cache_ops
Previous by thread: Re: signals logged / [RFC] log out-of-virtual-memory events
Next by thread: Re: signals logged / [RFC] log out-of-virtual-memory events
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]