diff options
| author | Qi Wang <interwq@gwu.edu> | 2018-05-02 14:35:31 -0700 |
|---|---|---|
| committer | Qi Wang <interwq@gmail.com> | 2018-05-02 15:08:49 -0700 |
| commit | c5b72a92cc40a0f95e13cb3e3bb4fba0f7ef36c3 (patch) | |
| tree | 36c8baffcd323996cd1de4163374c97c2912eb9c | |
| parent | a32b7bd5676e669821d15d319f686c3add451f4b (diff) | |
| download | platform_external_jemalloc_new-c5b72a92cc40a0f95e13cb3e3bb4fba0f7ef36c3.tar.gz platform_external_jemalloc_new-c5b72a92cc40a0f95e13cb3e3bb4fba0f7ef36c3.tar.bz2 platform_external_jemalloc_new-c5b72a92cc40a0f95e13cb3e3bb4fba0f7ef36c3.zip | |
Fix a typo in INSTALL.md.
| -rw-r--r-- | INSTALL.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -269,7 +269,7 @@ any of the following arguments (not a definitive list) to 'configure': Disable the initial-exec TLS model for jemalloc's internal thread-local storage (on those platforms that support explicit settings). This can allow - jemalloc to be dynamically loaded after program starup (e.g. using dlopen). + jemalloc to be dynamically loaded after program startup (e.g. using dlopen). Note that in this case, there will be two malloc implementations operating in the same process, which will almost certainly result in confusing runtime crashes if pointers leak from one implementation to the other. |