diff options
| author | Rafael Fontenelle <rafaelff@gnome.org> | 2019-04-07 06:53:38 -0300 |
|---|---|---|
| committer | Atomic Bot <atomic-devel@projectatomic.io> | 2019-04-08 12:50:42 +0000 |
| commit | 95e692794b7e4116e98a41644d77b7e8a2557d21 (patch) | |
| tree | c804f20e79ef76c25fdcb6aa08b6017897698138 /common/valgrind-private.h | |
| parent | af97b3db2f4a14a896163426f8a4189606d39e09 (diff) | |
| download | flatpak-95e692794b7e4116e98a41644d77b7e8a2557d21.tar.gz | |
Fix misspellings
Closes: #2807
Approved by: matthiasclasen
Diffstat (limited to 'common/valgrind-private.h')
| -rw-r--r-- | common/valgrind-private.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/common/valgrind-private.h b/common/valgrind-private.h index 5aed0dfc..4420d301 100644 --- a/common/valgrind-private.h +++ b/common/valgrind-private.h @@ -1673,7 +1673,7 @@ typedef /* NB 9 Sept 07. There is a nasty kludge here in all these CALL_FN_ macros. In order not to trash the stack redzone, we need to drop %rsp by 128 before the hidden call, and restore afterwards. The - nastyness is that it is only by luck that the stack still appears + nastiness is that it is only by luck that the stack still appears to be unwindable during the hidden call - since then the behaviour of any routine using this macro does not match what the CFI data says. Sigh. |