public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Ben Gardiner <BenGardiner@nanometrics.ca>
Cc: GCJ <java@gcc.gnu.org>
Subject: Re: libSegFault.so and gcj
Date: Fri, 15 May 2009 09:17:00 -0000	[thread overview]
Message-ID: <4A0D3327.3080308@redhat.com> (raw)
In-Reply-To: <4A0C40E7.6080907@redhat.com>

Andrew Haley wrote:
> Ben Gardiner wrote:
> 
>> We are running a gcj-compiled application on an embedded platform
>> (MPC852T). For reference our versions are gcc-4.0.1, glibc-2.3.3 and
>> linux-2.4.24 -- I know these versions are ancient, but please don't stop
>> reading here.
>>
>> We sometimes encounter segfaults in our application; that is to say that
>> it will terminate with 'Segmentation fault' on the console and return
>> 139. These occur rather infrequently, and we have yet to find a reliable
>> way to reproduce them. To make things more difficult, we do not have
>> room for core dumps on our filesystem.
>>
>> I thought that we could get the some information about these segfaults
>> by using the preload library libSegFault.so; I tested it and integrated
>> it with our init scripts and let it loose into our releases hoping that
>> a backtrace or two would come back to me. None did; there was no output
>> produced by libSegFault.so at all.
>>
>> I think that since gcj registers its own segfault handler which
>> translates segv signals into NullPointerExceptions, the original signals
>> never make it to libSegfault's handler. Gcj registers its handler,
>> catch_segv (from prims.cc:146 in our version of gcj), in INIT_SEGV
>> (powerpc-signal.h:62) called from _Jv_CreateJavaVM (prims.cc:1211). Here
>> is a snippet of INIT_SEGV:
>>
>> #define INIT_SEGV                            \
>> do                                    \
>>  {                                    \
>>    struct kernel_old_sigaction kact;                    \
>>    kact.k_sa_handler = catch_segv;                    \
>>    kact.k_sa_mask = 0;                            \
>>    kact.k_sa_flags = 0;                        \
>>    if (syscall (SYS_sigaction, SIGSEGV, &kact, NULL) != 0)        \
>>      __asm__ __volatile__ (".long 0");                    \
>>  }                                    \
>> while (0)
>>
>> and of catch_segv:
>>
>> SIGNAL_HANDLER (catch_segv)
>> {
>>  java::lang::NullPointerException *nullp
>>    = new java::lang::NullPointerException;
>>  unblock_signal (SIGSEGV);
>>  MAKE_THROW_FRAME (nullp);
>>  throw nullp;
>> }
>>
>> I don't know a whole lot about signal handlers -- please correct me if
>> I'm wrong: I think that since the syscall (SYS_sigaction,...) passes
>> NULL as the fourth argument, that gcj is disregarding the presence of
>> any previously registered signal handlers.
> 
> Correct.  gcj treats all segfaults as null pointer exceptions.
> 
>> I also think that since the
>> flags are zero that catch_segv is executed on the same stack as the
>> process that threw the signal instead of the alternate stack.
> 
> Also correct.
> 
>> I reason from this that the segfaults are likely stack overflows. Could
>> anyone confirm this?
> 
> That's quite possible.  Do you not have a debugger?
> 
> Clearly if it really is a stack overflow then you're not going to be
> able to call the null pointer handler.  There is a way around this,
> though.  If you use the -fstack-check option gcc generates a probe
> at the start of every method that writes a zero some 12kbytes below
> the stack pointer.  This will give you enough stack space for the
> catch_segv handler to run.

Although you'll have to make very sure that the catch_segv handler is built
*without* the -fstack-check option !

One other thing that you can use to detect stack overflow: compile with
`-finstrument-functions'.  This might be the easiest way to do it.

Andrew.



Andrew.

  reply	other threads:[~2009-05-15  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 15:28 Ben Gardiner
2009-05-14 16:04 ` Andrew Haley
2009-05-15  9:17   ` Andrew Haley [this message]
2009-05-15 20:23   ` Ben Gardiner
2009-05-15 20:49     ` David Daney
2009-05-14 16:10 ` David Daney

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=4A0D3327.3080308@redhat.com \
    --to=aph@redhat.com \
    --cc=BenGardiner@nanometrics.ca \
    --cc=java@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).