public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "Hans dot Boehm at hp dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/14767] gcjlib under FreeBSD does not forward SIGSEGV to SA_SIGINFO handler Date: Wed, 07 Apr 2004 20:30:00 -0000 [thread overview] Message-ID: <20040407202957.31015.qmail@sources.redhat.com> (raw) In-Reply-To: <20040329041331.14767.andrew.gray@anu.edu.au> ------- Additional Comments From Hans dot Boehm at hp dot com 2004-04-07 20:29 ------- I would generally like to see this go in roughly as is. Thanks for tracking this down. I think the GC_reset_fault_handler problem is much more serious than the remaining one. You really only need GC_write_fault_handler to pass through SIGSEGV if both: - The collector is running in incremental mode. - The client has a SIGSEGV handler for other reasons. I don't think either libgcj or Mono officially support incremental mode. (This has implications on other library code.) For now, a FIXME comment for the second bug is probably sufficient. (Of course, a proper patch would be gratefully accepted, too. A general clean-up patch for this code wouldn't hurt either :-) ) I have one question about the patch: For the hunk at line 121, is there really a reason to exclude FREEBSD? This worries me, since the upstream source replaces this test with one for a "UNIX- LIKE" OS. Can a plain setjmp be used to jump out of a signal handler on FreeBSD? Is sigsetjmp( ..., 1) appreciably slower than plain setjmp? -- What |Removed |Added ---------------------------------------------------------------------------- CC| |Hans dot Boehm at hp dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14767
next prev parent reply other threads:[~2004-04-07 20:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-29 4:13 [Bug libgcj/14767] New: " andrew dot gray at anu dot edu dot au 2004-03-30 0:41 ` [Bug libgcj/14767] " andrew dot gray at anu dot edu dot au 2004-03-30 2:45 ` ljrittle at gcc dot gnu dot org 2004-03-30 7:40 ` andrew dot gray at anu dot edu dot au 2004-04-07 20:30 ` Hans dot Boehm at hp dot com [this message] 2004-04-08 0:32 ` andrew dot gray at anu dot edu dot au 2004-04-19 7:18 ` andrew dot gray at anu dot edu dot au
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040407202957.31015.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).