Thank you for the contributions related to W^X.
In regards to signed releases, well, I can't make Perl 6 developers do
anything they don't want to do. I can explain the process or commands
or even manage it myself (which would admittedly be a bit strange,
having made no other contributions) but if
I just committed a little change to MoarVM that'll turn off the jit if
we notice we're not allowed to turn a page executable.
https://github.com/MoarVM/MoarVM/commit/b07acdfd92a88d1e40ad42c1c853922b20f1a056
now it won't crash if deny_execmem is turned on. it'll just be slower.
There's appare
On 2017-07-29 18:38, Timo Paulssen wrote:
However, an executable heap is still necessary even though an
executable stack is not needed when MoarVM built to use libffi 3.1 or
later:
This is most likely due to the jit, which allocates a frame, generates
machine code into it, then jumps into it. Ca
Great find on libffi! This ought to be a good way forward for
security-focused distros.
On 30/07/17 00:30, Mark Montague wrote:
> However, an executable heap is still necessary even though an
> executable stack is not needed when MoarVM built to use libffi 3.1 or
> later:
>
> [markmont@f26docker r
On 2017-07-29 08:28, Timo Paulssen wrote:
>> The reliance on W^X violating behavior is something I would like >> to see
removed,
Actually what they are refering to is that dyncall and libffi both
require an executable stack. We can't get around that without making
changes to libffi and dyncall
On Windows 10 rakudo star 2017.07 I get
\"foo\"
Proc.new(in => IO::Pipe, out => IO::Pipe, err => IO::Pipe, exitcode =>
0, signal => 0, command => ["echo \"foo\""])
whereas on FreeBSD 10 I get
foo
only (no quotes or Proc.new structure)
S
On 29 July 2017 at 16:29, Holli Holzer wrote:
> # New T
On Windows 10 rakudo star 2017.07 I get
\"foo\"
Proc.new(in => IO::Pipe, out => IO::Pipe, err => IO::Pipe, exitcode =>
0, signal => 0, command => ["echo \"foo\""])
whereas on FreeBSD 10 I get
foo
only (no quotes or Proc.new structure)
S
On 29 July 2017 at 16:29, Holli Holzer wrote:
> # New T
I can't reproduce on Windows 10 Professional.
Was there a previous Rakudo Star install present?
You could try
cd %USERPROFILE%
rd /s .zef
rs /s .perl6
and rerunning.
S
On 29 July 2017 at 18:08, Richard Loveland wrote:
> # New Ticket Created by Richard Loveland
> # Please include the string
I can't reproduce on Windows 10 Professional.
Was there a previous Rakudo Star install present?
You could try
cd %USERPROFILE%
rd /s .zef
rs /s .perl6
and rerunning.
S
On 29 July 2017 at 18:08, Richard Loveland wrote:
> # New Ticket Created by Richard Loveland
> # Please include the string
# New Ticket Created by Holli Holzer
# Please include the string: [perl #131814]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131814 >
good localtime()
I was told to write here after a conversation on irc. when i run the
fo
# New Ticket Created by Richard Loveland
# Please include the string: [perl #131815]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131815 >
$ zef search doc
No such method 'subst' for invocant of type 'Any'
in method ver
Am 29.07.2017 um 14:28 schrieb Timo Paulssen:
Actually what they are refering to is that dyncall and libffi both
require an executable stack. We can't get around that without making
changes to libffi and dyncall, sadly.
Ah okay, that was outside the bounds of my knowledge.
And I agree it's u
>> The reliance on W^X violating behavior is something I would like >> to see
>> removed, > > That behaviour does not exist. The binary blobs
aren't created as > part of the normal build process, and even if they
were, the code > writes the bytecodes to disk, it does not directly
execute them.
Ac
Am 29.07.2017 um 05:20 schrieb R0b0t1:
Most issues I have seen that arise with submodules come from people
trying to treat the submodule directory in a way that is different
than other objects tracked by Git. If you treat it like a source file
you're tracking most problems should disappear, at le
On Thu, Jul 27, 2017 at 12:43 PM, Will Coleda wrote:
> I agree, that seems like pointless editorializing.
>
> If you can open a ticket at perl6/doc/issues on github, I'll remove
> that sentence this evening. (or someone can beat me to it.)
>
>
OK, it's done:
https://github.com/perl6/doc/issues/1
Submodules *are* already used as I said previously or would be obvious
to anyone reading the code. I'd recommend doing the latter before
posting.
Anyway I'm not replying to this thread anymore since it's obvious we
are getting to the point of diminishing returns.
If you have improvements please s
16 matches
Mail list logo
