mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: froese@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] signal handler defaulting fix ...
Date: 03 Jul 2004 15:54:00 +0200	[thread overview]
Message-ID: <9C8lzYXmw-B@khms.westfalen.de> (raw)
In-Reply-To: <2cfBL-6uJ-9@gated-at.bofh.it>

froese@gmx.de (Edgar Toernig)  wrote on 29.06.04 in <2cfBL-6uJ-9@gated-at.bofh.it>:

> Not the signal part.  It was written for libc5.  There, signals set
> with signal(2) were reset when raised (SysV-style).  Leaving such a
> signal handler with longjmp was perfectly valid.
>
> Glibc2 changed the rules: signals set with signal(2) are not reset
> but blocked during delivery (BSD-style).  It worked for a while
> because the kernel ignored the sigmask for some signals.
>
> So, if one is to blame then glibc2 by breaking compatibility.

You might want to study /usr/include/signal.h and /usr/include/feature.h.

And then you might try stuff like -D_SVID_SOURCE or -Dsignal=sysv_signal,  
for example.

And stop blaming glibc for your failures.

MfG Kai

       reply	other threads:[~2004-07-04  4:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2cfBL-6uJ-9@gated-at.bofh.it>
2004-07-03 13:54 ` Kai Henningsen [this message]
2004-06-28 21:34 Davide Libenzi
2004-06-28 21:40 ` Andrew Morton
2004-06-28 21:49   ` Linus Torvalds
2004-06-28 21:55     ` Davide Libenzi
2004-06-28 22:08       ` Linus Torvalds
2004-06-28 22:13         ` Davide Libenzi
2004-06-29  1:24         ` Edgar Toernig
2004-06-29 12:02           ` Jörn Engel
2004-06-28 21:49   ` Jörn Engel

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=9C8lzYXmw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=froese@gmx.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®