Gnash and aslr-fix
 

On 25 Feb 2012 at 10:09, Christian Apeltauer wrote:

hi,

> The code wasn't exactly the same as expected by firefox's
> ff9-aslr-fix.patch, but I was able to port it to gnash. gnash works
> now. Nonetheless I would like to have my patch to be reviewed by
> someone who has a better understanding of what's going on.

while the patch looks good me, can't you simply configure gnash to not use
the embedded jemalloc copy but the systemwide one (which was fixed 2 years
ago or so)?

Gnash and aslr-fix
 

On Sat, 25 Feb 2012 11:06:06 +0200
"PaX Team" <pageexec@freemail.hu> wrote:

> On 25 Feb 2012 at 10:09, Christian Apeltauer wrote:
>
> hi,
>
> > The code wasn't exactly the same as expected by firefox's
> > ff9-aslr-fix.patch, but I was able to port it to gnash. gnash works
> > now. Nonetheless I would like to have my patch to be reviewed by
> > someone who has a better understanding of what's going on.
>
> while the patch looks good me, can't you simply configure gnash to
> not use the embedded jemalloc copy but the systemwide one (which was
> fixed 2 years ago or so)?
>
>

I added --disable-jemalloc to $myconf and gnash worked without the
patch.
Thanks

--

Gnash and aslr-fix
 

On 26 Feb 2012 at 11:01, Christian Apeltauer wrote:

> > while the patch looks good me, can't you simply configure gnash to
> > not use the embedded jemalloc copy but the systemwide one (which was
> > fixed 2 years ago or so)?
>
> I added --disable-jemalloc to $myconf and gnash worked without the
> patch.

you should probably open a bug about and let the maintainers fix the ebuild for everyone ;).

Gnash and aslr-fix
 

On 02/26/2012 05:44 AM, PaX Team wrote:

On 26 Feb 2012 at 11:01, Christian Apeltauer wrote:


while the patch looks good me, can't you simply configure gnash to
not use the embedded jemalloc copy but the systemwide one (which was
fixed 2 years ago or so)?


I added --disable-jemalloc to $myconf and gnash worked without the
patch.


you should probably open a bug about and let the maintainers fix the ebuild for everyone ;).



I don't mind discussing bugs on the list, but I strongly encourage
people to open up bug reports because emails come and go, but reports in
bugzilla are organized in a way that makes it convenient for devs to
know what needs to be done next. When my bugs get into the dozens,
there's no way I can fish through emails to find stuff.


http://www.gentoo.org/doc/en/bugzilla-howto.xml

--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197

Gnash and aslr-fix
 

On Sun, 26 Feb 2012 12:44:29 +0200
"PaX Team" <pageexec@freemail.hu> wrote:

> On 26 Feb 2012 at 11:01, Christian Apeltauer wrote:
>
> > > while the patch looks good me, can't you simply configure gnash to
> > > not use the embedded jemalloc copy but the systemwide one (which
> > > was fixed 2 years ago or so)?
> >
> > I added --disable-jemalloc to $myconf and gnash worked without the
> > patch.
>
> you should probably open a bug about and let the maintainers fix the
> ebuild for everyone ;).
>
>

Some good news for all PAX users: According to gnash's bucktracker the
patch has been committed to gnash's git repository.
https://savannah.gnu.org/bugs/?35635

--