From: John Richard Moser <nigelenki@comcast.net>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Tue, 06 Jul 2004 11:55:16 -0400 [thread overview]
Message-ID: <40EACB64.2010503@comcast.net> (raw)
In-Reply-To: <20040705231131.GA5958@merlin.emma.line.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The only thing I've seen kill java like that would be NX things, such as
the NX patch mentioned in an earlier thread; execshield; or PaX. I saw
some talk about possibly enabling NX by default; but I don't see this in
the -mm6 list, and I have no idea where the bk patch list is. I
wouldn't expect either Linus or Andrew to have decided to merge an NX
patch in at this stage; but it's a possibility.
Andrew? Has anything like that been added in the bk tree?
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.
|
| Is there any particular change I should try backing out?
|
| TIA,
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA6stihDd4aOud5P8RAnSWAJsGGWL61RC+GIiKk083w6tN5minSQCfSzb4
tstDqu+7FnIyeCSrfSBPrS8=
=pOq9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-06 15:55 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 [this message]
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
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=40EACB64.2010503@comcast.net \
--to=nigelenki@comcast.net \
--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