diff options
| author | bors[bot] <bors[bot]@users.noreply.github.com> | 2017-07-19 05:32:22 +0000 |
|---|---|---|
| committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2017-07-19 05:32:22 +0000 |
| commit | 3d24ae9588ebad1e495bedc909a226c84662a4c2 (patch) | |
| tree | 7bf90108d9ade894cdcfb250e2ea93df7ae6f9f5 /.travis.yml | |
| parent | 3acc24c1093bf38424c0f0348b71b08b337fbec6 (diff) | |
| parent | bba9e436393e3606bfe19a2a1d40c849a9242f4a (diff) | |
| download | nix-3d24ae9588ebad1e495bedc909a226c84662a4c2.zip | |
Merge #686
686: Fix special ptraces r=Susurrus
In #614 we added specializations of `ptrace()` that added more type safety. As part of this, the `UnsupportedOperation` error was introduced for the requests that are covered by specialized versions so they couldn't be used with the general `ptrace()`. Unfortunately, no tests were added with this PR and so it slipped through that you could not do those operations at all anymore: `ptrace()` reported `UnsupportedOperation` for them and `ptrace_*` called `ptrace`, not `ffi::ptrace` and so also reported `UnsupportedOperation`! Whoops!
This minimally-invasive surgery corrects this by adding tests that call all the specialized `ptrace_*` ignoring the return value save checking for `UnsupportedOperation`. It also changes the functions calls to use `ffi::ptrace()` directly to fix the bug.
As this was never a bug in a released version of `nix`, there's no need for a changelog entry here.
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions