[Mono-devel-list] syscall vs. sigaction

Dietmar Maurer dietmar at maurer-it.com
Wed Mar 26 12:12:53 EST 2003

The problem is that the libpthread overwrites sigaction, and does not
allow us to catch certain signals. So we need to use syscall directly to
catch the signal. Unfortunately this is very system/version dependent.

Maybe you can take a look on the implementation of libpthread on your 
system to see if it is possible to catch SIGUSR1/SIGRTMIN? What system
do you talk about? Does it have SIGRTMIN?

- Dietmar

On Thu, 2003-03-06 at 13:52, Michael Adams - CPX Tetra wrote:
> Hi All,
> In  mono/jit/jit.c
> Most of the lines:  g_assert (syscall (SYS_sigaction ....
> have been commented out and replaced with : g_assert (sigaction ....
> except for one line.
> Is this one call to syscall() supposed to be there, or should it be replace
> with the sigaction() call ?
> I'm asking as my system doesn't have a syscall() function however
> sigaction() works fine,
> so I have to change this line each time I get a newer version of mono.
> also,
> mono/jit/codegen.h  has the include: #include <sys/syscall.h>
> which my system lacks.  However, the code compiles fine if I comment this
> include out.
> If possible, could the configure define a _HAVE_SYS_SYSCALL_ or something ?
> cheers
> ----------------------------------------------------------------------------
> ------------
> Michael Adams
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list