1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
<!--
libexplain - Explain errno values returned by libc functions
Copyright (C) 2009, 2010 Peter Miller
Written by Peter Miller <pmiller@opensource.org.au>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or (at
your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
.hy 0
.ad l
<!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"
>
.nf
<html>
<head>
<title>
No Medium Found, 5.2
</title>
</head>
<body>
<table width="100%" >
<tr>
<td align="left" >
<a href="510-slide.html" >Prev</a>,
<a href="index.html" >Top</a>
</td><td align="right" >
<a href="500-notes.html#5.2" >Notes</a>,
<a href="530-slide.html" >Next</a>
</td>
</tr>
</table>
<h1 align="center" >
Strange and Interesting System Calls<br/>
EFAULT, Bad address
</h1>
<table align="center" ><tr><td>
If a system call only has one pointer argument, it is easy to figure out.
<blockquote><pre>
unlink(pathname = 0x7FFFDB0B49C9) failed, Bad address (14, EFAULT) because
pathname refers to memory that is outside the process's accessible address
space; this is more likely to be a software error (a bug) than it is to be a
user error
</pre></blockquote>
But what if there is more than one pointer argument?
<blockquote><pre>
rename(oldpath = "fred", newpath = 0x7FFFDB0B49C9) failed, Bad address (14,
EFAULT) because newpath refers to memory that is outside the process's
accessible address space; this is more likely to be a software error (a bug)
than it is to be a user error
</pre></blockquote>
The library does not disturb process signal handlers.
</td></tr></table>
</body>
</html>
|
