From: kernel <kernel@draper.net>
To: Elena Labruna <labruna@cli.di.unipi.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: longjmp problem
Date: Fri, 16 Feb 2001 00:42:07 -0600 [thread overview]
Message-ID: <20010216004207.A2097@draper.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0102120802270.3423-100000@delta19.cli.di.unipi.it>
In-Reply-To: <Pine.LNX.4.21.0102120802270.3423-100000@delta19.cli.di.unipi.it>; from Elena Labruna on Mon, Feb 12, 2001 at 08:10:01AM +0100
On Mon, Feb 12, 2001 at 08:10:01AM +0100, Elena Labruna wrote:
> I'm working with a C package written by other
> on a linux machine with kernel version 2.2.14,
> often in a calls of longjmp routine
> the system crash with a SIGSEGV signal.
>
> Anyone can tell me if it can be a kernel problem ?
>
> Elena Labruna.
>
Fwiw, we issue(d) longjmp() in signal catching functions (including
segv) without difficulty on 2.2.14 kernels. Perhaps your application
is not first calling setjmp() to save the stack context?
Reed,
prev parent reply other threads:[~2001-02-16 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 7:10 longjmp problem Elena Labruna
2001-02-14 19:38 ` Alan Cox
2001-02-16 6:42 ` kernel [this message]
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=20010216004207.A2097@draper.net \
--to=kernel@draper.net \
--cc=labruna@cli.di.unipi.it \
--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