On 5/16/2019 9:48 PM, Anshuman Khandual wrote:
On 05/17/2019 09:38 AM, Jane Chu wrote:
Some user who install SIGBUS handler that does longjmp out
What the longjmp about ? Are you referring to the mechanism of catching the
signal which was registered ?
Yes.
thanks,
-jane
Thanks Vishal and Naoya!
-jane
On 5/20/2019 3:21 AM, Naoya Horiguchi wrote:
On Fri, May 17, 2019 at 10:18:02AM +0530, Anshuman Khandual wrote:
On 05/17/2019 09:38 AM, Jane Chu wrote:
Some user who install SIGBUS handler that does longjmp out
What the longjmp about ? Are you referring to
On Fri, May 17, 2019 at 10:18:02AM +0530, Anshuman Khandual wrote:
>
>
> On 05/17/2019 09:38 AM, Jane Chu wrote:
> > Some user who install SIGBUS handler that does longjmp out
>
> What the longjmp about ? Are you referring to the mechanism of catching the
> signal which was registered ?
AFAIK,
On Thu, 2019-05-16 at 22:08 -0600, Jane Chu wrote:
> Some user who install SIGBUS handler that does longjmp out
> therefore keeping the process alive is confused by the error
> message
> "[188988.765862] Memory failure: 0x1840200: Killing
>cellsrv:33395 due to hardware memory corruption"
>
On 05/17/2019 09:38 AM, Jane Chu wrote:
> Some user who install SIGBUS handler that does longjmp out
What the longjmp about ? Are you referring to the mechanism of catching the
signal which was registered ?
> therefore keeping the process alive is confused by the error
> message
>
Some user who install SIGBUS handler that does longjmp out
therefore keeping the process alive is confused by the error
message
"[188988.765862] Memory failure: 0x1840200: Killing
cellsrv:33395 due to hardware memory corruption"
Slightly modify the error message to improve clarity.
6 matches
Mail list logo