Re: Question about CR_SIGNUM

From: Paul H. Hargrove (PHHargrove_at_lbl_dot_gov)
Date: Sun Jul 12 2009 - 00:28:41 PDT

  • Next message: Jean-Jack M Riethoven: "Jean-Jack M Riethoven is out of the office."
    A SIG* name is just a name, but all the kernel source actually needs is
    the numbers.
    The Linux kernel defines 64 signals (1 to 64), of which the upper 32 are
    "realtime" signals that don't have any fixed names associated with them
    and are therefore safe to reuse in BLCR.
    
    CR_SIGNUM is not just "64" because some older kernels implemented only 1
    through 63. We determine at configure time if 63 or 64 is the correct
    value to use.
    
    -Paul
    
    李宏亮 wrote:
    > Hello,Professor:
    >
    > how can you define a new kernel signal for CR use without adding it
    > into the kernel source code(../signum.h) ?
    >
    > #define SIGABRT 1 /* Abnormal termination. */
    > #define SIGFPE 2 /* Erroneous arithmetic operation. */
    > #define SIGILL 3 /* Illegal instruction. */
    > -#define SIGINT 3 /* Interactive attention signal. */
    >
    >
    > I see this:
    >
    > "#define CR_SIGNUM @CR_SIGNUM@" in Blcr_common.h
    >
    > please teach me this usage , thank you
    >
    >
    >
    >
    >
    > ===============================================
    > 快来和我一起享受TOM免费邮箱吧!看看除了1.5G,还有什么?
    > <http://bjcgi.163.net/cgi-bin/newreg.cgi?%0Arf=050602>
    > ===============================================
    >
    
    
    -- 
    Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
    Future Technologies Group                 Tel: +1-510-495-2352
    HPC Research Department                   Fax: +1-510-486-6900
    Lawrence Berkeley National Laboratory     
    

  • Next message: Jean-Jack M Riethoven: "Jean-Jack M Riethoven is out of the office."