46:
means that while a program cannot overwrite the memory of other programs, a loose pointer can still cause strange behaviour within the application.
27:
49:
The term presumably comes from the programmer imagining the program following the wild pointer and dancing a
96:
23:
43:
39:
77:
90:
81:
63:
34:, or failures in other seemingly unrelated processes. In extreme situations,
31:
50:
42:
code, possibly causing data loss or system crashes. The advent of
62:
This article or an earlier version of it came from the
53:
on the core (an older term for memory) of a program.
8:
30:running out of bounds, often leading to a
7:
14:
38:may lead to the overwriting of
1:
16:Out-of-bounds pointer effects
113:
26:term for the effects of a
24:computer programming
80:" entry from the
104:
78:Fandango on core
44:protected memory
40:operating system
36:fandango on core
20:Fandango on core
112:
111:
107:
106:
105:
103:
102:
101:
87:
86:
73:
59:
17:
12:
11:
5:
110:
108:
100:
99:
89:
88:
85:
84:
72:
71:External links
69:
58:
55:
15:
13:
10:
9:
6:
4:
3:
2:
109:
98:
97:Software bugs
95:
94:
92:
83:
79:
75:
74:
70:
68:
67:
65:
56:
54:
52:
47:
45:
41:
37:
33:
29:
25:
21:
61:
60:
48:
35:
19:
18:
82:Jargon File
64:Jargon File
57:References
32:core dump
91:Category
51:fandango
28:pointer
22:is a
93::
76:"
66:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.