Re: Disturbing truss output

From: Paul Pluzhnikov (ppluzhnikov_at_earthlink.net)
Date: 05/10/03 

Date: Sat, 10 May 2003 03:03:17 GMT

Fletcher Glenn <f-g-l-e-n-n@quest.com> writes:

> KFWebb wrote:
> >
> > FLTBOUNDS 16279
> I can't speak to the other signals in your summary, but I
> am aware of a database company that used SIGSEGV to determine

IIRC, Java JIT-compiled code also exhibits similar access patterns.

Cheers, 

-- 
In order to understand recursion you must first understand recursion.

Relevant Pages

  • Re: gdb vs fortran RTL -- fight for SIGSEGV
    ... any chance to catch/handle the signal. ... SIGSEGV; that you've misinterpreted what you observed, ... Try gdb 'catch fork' command to find out. ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: Programmatic stack trace?
    ... > SEGV and try to generate a stack trace form a signal handler. ... Once SIGSEGV is hit, the state of your program is undefined (unless ... which will invoke "pstack exe core" should your exe ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: SIGSEGV handled within JVM?
    ... build under truss and noticed that the JVM seems to catch a seg fault ... No. Sun JVM's do that (at least on Solaris and Linux) while running ... SIGSEGV and deal with it, it's not possible to be sure you're not ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.solaris)
  • Re: dlopen and SIGSEGV
    ... > function of the library send a SIGSEGV signal. ... You got a loop in your signal handler, ... handler will simply restart the instruction that caused SIGSEGV, ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)