Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
C
capnproto
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
capnproto
Commits
715325fa
Commit
715325fa
authored
Nov 07, 2015
by
Kenton Varda
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add comment explaining totally weird behavior of siginfo.ssi_ptr.
parent
90c04962
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
0 deletions
+7
-0
async-unix.c++
c++/src/kj/async-unix.c++
+7
-0
No files found.
c++/src/kj/async-unix.c++
View file @
715325fa
...
...
@@ -458,6 +458,13 @@ static siginfo_t toRegularSiginfo(const struct signalfd_siginfo& siginfo) {
// we write the pointer, we'll end up with the right value for the int? Presumably the
// two fields of signalfd_siginfo are actually extracted from one of these unions
// originally, so actually contain redundant data? Better write some tests...
//
// Making matters even stranger, siginfo.ssi_ptr is 64-bit even on 32-bit systems, and
// it appears that instead of doing the obvious thing by casting the pointer value to
// 64 bits, the kernel actually memcpy()s the 32-bit value into the 64-bit space. As
// a result, on big-endian 32-bit systems, the original pointer value ends up in the
// *upper* 32 bits of siginfo.ssi_ptr, which is totally weird. We play along and use
// a memcpy() on our end too, to get the right result on all platforms.
memcpy
(
&
result
.
si_ptr
,
&
siginfo
.
ssi_ptr
,
sizeof
(
result
.
si_ptr
));
break
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment