Re: Catching SIGSEGV with signal() in 2.6
From: Chris Friesen (cfriesen_at_nortelnetworks.com)
Date: 04/05/04
- Previous message: Ray Bryant: "Re: [Lse-tech] RE: [PATCH] HUGETLB memory commitment"
- In reply to: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Next in thread: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Reply: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 05 Apr 2004 15:16:35 -0400 To: Jamie Lokier <jamie@shareable.org>
Jamie Lokier wrote:
> bero@arklinux.org wrote:
>
>>... doesn't seem to be possible anymore.
>>
>>See http://www.openoffice.org/issues/show_bug.cgi?id=27162
>>
>>Is this change intentional, or a bug?
>
>
> On 2.6.3, x86, SIGSEGV is being caught just fine in my test program,
> with the correct fault address, with or without SA_SIGINFO.
SA_SIGINFO implies sigaction(). The original poster was talking about
signal().
That said, it seems to work with 2.6.4 on ppc32.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Ray Bryant: "Re: [Lse-tech] RE: [PATCH] HUGETLB memory commitment"
- In reply to: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Next in thread: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Reply: Jamie Lokier: "Re: Catching SIGSEGV with signal() in 2.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|