public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "andrew dot gray at anu dot edu dot au" <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: Tue, 30 Mar 2004 00:41:00 -0000	[thread overview]
Message-ID: <20040330004147.28662.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040329041331.14767.andrew.gray@anu.edu.au>


------- Additional Comments From andrew dot gray at anu dot edu dot au  2004-03-30 00:41 -------
Created an attachment (id=6014)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=6014&action=view)
Patch to os_dep.c and gcconfig.h to fix this bug

This patch fixes the problem reported here.  The patch is against the
gcc-3.4-20040310 snapshot.  After applying the patch the test program produces
the following:

$ ./gcjsigsegv	j
Using Java
Caught fault
sig = 11
info = 0xbfbff7dc
info->si_code = 12
Exiting

However, the changes in the patch do not appear to completely deal with
supporting FreeBSD's signal handling.  It appears that the reported bug
was due to GC_fault_reset_handler not reinstating a SA_SIGINFO handler
correctly.  This patch fixes that problem.  However, the code in
GC_write_fault_handler should determine the style to the old handler
and use that style when calling it.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14767


  reply	other threads:[~2004-03-30  0:41 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 ` andrew dot gray at anu dot edu dot au [this message]
2004-03-30  2:45 ` [Bug libgcj/14767] " 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
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=20040330004147.28662.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: link
Be 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).