aboutsummaryrefslogtreecommitdiffstats
path: root/HOWTO/INSTALL-ANDROID.md
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2014-05-09 12:35:22 +0200
committerBjörn Gustavsson <[email protected]>2014-06-04 16:43:17 +0200
commited06dd12ea74018b902a2c4c7924313d23cedb75 (patch)
tree4d4ac5c25f19119d447182984d1cfb8e03aff245 /HOWTO/INSTALL-ANDROID.md
parent32f33d9897261b15573e7e606d990e60e294fc22 (diff)
downloadotp-ed06dd12ea74018b902a2c4c7924313d23cedb75.tar.gz
otp-ed06dd12ea74018b902a2c4c7924313d23cedb75.tar.bz2
otp-ed06dd12ea74018b902a2c4c7924313d23cedb75.zip
Make pre-loaded modules permanently sticky
Modules in the kernel, stdlib, and compiler applications are by default "sticky", meaning that the code server will refuse to re-load them. The pre-loaded modules (those that are part of the run-time system itself, such as 'erlang') are, however, not sticky. They used to be sticky a long time ago when the pre-loaded modules were part of the kernel application. Now they are part of the erts application. Since re-loading a pre-loaded module can be catastrophic (especially re-loading the 'erlang' module), the pre-loaded modules must be sticky. Furthermore, it should not be allowed to unstick them. The sticky_dir/1 test case in code_SUITE is never actually run and is broken. Rewrite it.
Diffstat (limited to 'HOWTO/INSTALL-ANDROID.md')
0 files changed, 0 insertions, 0 deletions