Re: CVS commit: src/usr.bin/crunch/crunchgen

[christos%astron.com@localhost (Christos Zoulas)]

In article <20190213065626.GA22091%mail.duskware.de@localhost>,
Martin Husemann  <martin%duskware.de@localhost> wrote:
>On Tue, Feb 12, 2019 at 09:20:23PM -0000, Christos Zoulas wrote:
>> Well, regardless of what the right permissions of .eh_frame are,
>> we could just nuke the code and default to the "new" behavior...
>> We can then put back the varasm.c change...
>> This of course needs to be evaluated carefully.
>
>Why would anyone modify the eh frame list at runtime? Or is any other
>writable data placed there on purpose? I didn't see any, and if - wouldn't
>it better go into a separate section?

I understand that, this is why I am saying that removing the code that
triggers the bug, we can restore the varasm change that makes the segment
readonly... We can then take our time (or have the gcc folks) fix the
underlying issue.

christos