2.2.17pre15 and SA_SIGINFO

• Next message: wingel@t1.ctrl-c.liu.se: "Re: [patch?] Re: Do ramdisk exec's map direct to buffer cache?"
• Previous message: Alan Cox: "Re: a kernel oops. must help linux be all it can be"
• Next in thread: Miquel van Smoorenburg: "Re: 2.2.17pre15 and SA_SIGINFO"
• Reply: Miquel van Smoorenburg: "Re: 2.2.17pre15 and SA_SIGINFO"
• Reply: Andries Brouwer: "Re: 2.2.17pre15 and SA_SIGINFO"
• Maybe reply: Philip Blundell: "Re: 2.2.17pre15 and SA_SIGINFO"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello all,

I have a program which relies on being able to derive the address of a SIGSEGV. To do that, I use the SA_SIGINFO option to sigaction() and read out the faulting address from the si_addr parameter of the siginfo structure (second argument.) I also check si_code for SEGV_ACCERR.

Under 2.4 kernels, this works great. However, under 2.2.17pre15 (I downgraded because of stability problems) and glibc 2.1.2, si_code and si_addr are both 0. Is this simply unimplemented in 2.2 kernels, or is this a bug?

        -hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: wingel@t1.ctrl-c.liu.se: "Re: [patch?] Re: Do ramdisk exec's map direct to buffer cache?"
• Previous message: Alan Cox: "Re: a kernel oops. must help linux be all it can be"
• Next in thread: Miquel van Smoorenburg: "Re: 2.2.17pre15 and SA_SIGINFO"
• Reply: Miquel van Smoorenburg: "Re: 2.2.17pre15 and SA_SIGINFO"
• Reply: Andries Brouwer: "Re: 2.2.17pre15 and SA_SIGINFO"
• Maybe reply: Philip Blundell: "Re: 2.2.17pre15 and SA_SIGINFO"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Aug 07 2000 - 21:00:07 EST