| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This is mostly a pure refactoring.
Except for the buggy cases when calling erlang:halt() with a positive
integer in the range -(INT_MIN+2) to -INT_MIN that got confused with
ERTS_ABORT_EXIT, ERTS_DUMP_EXIT and ERTS_INTR_EXIT.
Outcome OLD erl_exit(n, ) NEW erts_exit(n, )
------- ------------------- -------------------------------------------
exit(Status) n = -Status <= 0 n = Status >= 0
crashdump+abort n > 0, ignore n n = ERTS_ERROR_EXIT < 0
The outcome of the old ERTS_ABORT_EXIT, ERTS_INTR_EXIT and
ERTS_DUMP_EXIT are the same as before (even though their values have
changed).
|
|
|
|
which does a deliberate deref of null pointer which is caught by
a SEGV signal handler to resume crash dumping.
|
|
Invalid read of size 8
(Address 0x61f7730 is 144 bytes inside a block of size 151 alloc'd)
Suspected: rc4_encrypt_with_state:2321 (-> 0x11B168F5) [crypto.c]
Stackdump:
RC4:??? (-> 0x11DAA060) [/lib/libcrypto.so.0.9.8]
rc4_encrypt_with_state:2321 (-> 0x11B168F5) [crypto.c]
process_main:3524 (-> 0x58D975) [beam_emu.c]
sched_thread_func:7672 (-> 0x4C131E) [erl_process.c]
thr_wrapper:106 (-> 0x656F68) [ethread.c]
start_thread:300 (-> 0x57019C9) [pthread_create.c]
|
|
|
|
Invalid write of size 8
(Address 0x84a63c0 is not stack'd, malloc'd or (recently) free'd)
Suspected: AES_cbc_encrypt:??? (-> 0xD7489CF) [/lib/libcrypto.so.0.9.8]
|
|
to work even when compiler does aggressive function inlining
|
|
|
|
* sverk/valgrind-async-thr-suppression:
erts: Add valgrind suppression for async thread bound data
|
|
|
|
This leak is harmless as the beam process is about to exit anyway.
|
|
|
|
Fix for 5dcee558b61f0f5dd70e18a530a2bb97c479aab5
|
|
|
