On 10/07/2014 04:39 PM, Matthew LeGendre wrote:
>
> On Tue, 7 Oct 2014, Josh Stone wrote:
>> I've been thinking about improving the selinux story -- right now we
>> must allow execmem/execstack because of the RWX memory maps. I'd like
>> to try separating this into proper code (R-X) and data (RW-
On Tue, 7 Oct 2014, Josh Stone wrote:
I've been thinking about improving the selinux story -- right now we
must allow execmem/execstack because of the RWX memory maps. I'd like
to try separating this into proper code (R-X) and data (RW-) maps for
inferior allocs. The API appears to already all
On 10/07/2014 09:26 AM, Bill Williams wrote:
> Two things here:
>
> 1) Dyninst 8.2.1 is coming soon, pending evaluation of fixes for a
> couple more bugs that have been reported in 8.2.0.
Please do push commits before the actual release, so interested parties
like myself may review the changes.
Two things here:
1) Dyninst 8.2.1 is coming soon, pending evaluation of fixes for a
couple more bugs that have been reported in 8.2.0.
2) We're looking at potential API-breaking changes that have been
floating around our TODO list, as we've got at least one good reason to
break the API (loop
