4 ms·

1. assert the integer's post condition. works best if the integer is filled with an uninitialized pattern first. 2. something like CRT or dmalloc to catch the

1. assert the integer's post condition. works best if the integer is filled with an uninitialized pattern first. 2. something like CRT or dmalloc to catch the leak. not perfect but a good hint

monocasa 7y ago
The integer was set correctly, so it wouldn't have triggered an assertation. And valgrind didn't find the leak, so dlmalloc or CRT def would not have.
- sesuximo 7y ago
  I'm very surprised that memcheckers wouldn't catch this leak
  - monocasa 7y ago
    And yet, that's what it says on the article.
ksherlock 7y ago
So you would call thirdparty_process("whatever", &res); then assert that res == 1? On little endian architectures, it is 1. On big endian architectures, it's 0 which seems like a reasonable value as well.
- sesuximo 7y ago
  depends on context, but you could either assert a range of possible values or assert not dead
  - monocasa 7y ago
    What do you mean "not dead". It's a stack allocated variable.
    - sesuximo 7y ago
      using a sentinel value in debug mode. in this case the assertion would probably not catch the sentinel, but you would recognize it in gdb