From: Go Taniguchi <go@turbolinux.co.jp>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, Con Kolivas <kernel@kolivas.org>,
Matthias Andree <matthias.andree@gmx.de>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Sat, 10 Jul 2004 20:41:15 +0900 [thread overview]
Message-ID: <40EFD5DB.3000100@turbolinux.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.56.0407091954160.22376@jjulnx.backbone.dif.dk>
Hi list.
Jesper Juhl wrote:
> On Fri, 9 Jul 2004, Con Kolivas wrote:
>
>
>>>On Tue, 6 Jul 2004, Matthias Andree wrote:
>>>>Hi,
>>>>
>>>>I've pulled from the linux-2.6 BK tree some post-2.6.7 version,
>>compiled
>>>>and installed it, and it breaks Java, standalone or plugged into
>>>>firefox, the symptom is that the application catches SIGKILL. This
>>>>didn't happen with stock 2.6.7 and doesn't happen with 2.6.6 either.
If I removed this changeset, java worked.
http://linux.bkbits.net:8080/linux-2.6/cset@1.1743
Is this "rt_sigsuspend() and sigaltstack() prototype change" right?
If so, how do we resolve user side?
next prev parent reply other threads:[~2004-07-10 11:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 23:11 post 2.6.7 BK change breaks Java? Matthias Andree
2004-07-06 15:55 ` John Richard Moser
2004-07-06 16:14 ` Matthias Andree
2004-07-06 17:49 ` John Richard Moser
2004-07-06 22:45 ` Andy Isaacson
2004-07-09 13:51 ` Jesper Juhl
2004-07-09 14:54 ` Con Kolivas
2004-07-09 16:37 ` José de Paula
2004-07-09 17:55 ` Jesper Juhl
2004-07-10 11:41 ` Go Taniguchi [this message]
2004-07-11 15:16 ` Jesper Juhl
2004-07-11 15:19 ` Con Kolivas
2004-07-11 15:35 ` Jesper Juhl
2004-07-11 15:35 ` Grzegorz Kulewski
2004-07-11 15:38 ` Jesper Juhl
2004-07-12 0:56 ` Jesper Juhl
2004-07-12 3:20 ` Brian Gerst
2004-07-12 3:57 ` Brian Gerst
2004-07-12 11:01 ` Jesper Juhl
2004-07-12 12:38 ` Brian Gerst
2004-07-12 14:05 ` Matthias Andree
2004-07-12 15:59 ` Linus Torvalds
2004-07-12 21:50 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 18:38 Ray Lee
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=40EFD5DB.3000100@turbolinux.co.jp \
--to=go@turbolinux.co.jp \
--cc=juhl-lkml@dif.dk \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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