File: TestAllocReplacement.cpp

package info (click to toggle)
firefox 147.0.2-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,683,484 kB
  • sloc: cpp: 7,607,246; javascript: 6,533,185; ansic: 3,775,227; python: 1,415,393; xml: 634,561; asm: 438,951; java: 186,241; sh: 62,752; makefile: 18,079; objc: 13,092; perl: 12,808; yacc: 4,583; cs: 3,846; pascal: 3,448; lex: 1,720; ruby: 1,003; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10; exp: 6
file content (75 lines) | stat: -rw-r--r-- 2,511 bytes parent folder | download | duplicates (14)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* vim: set ts=8 sts=2 et sw=2 tw=80: */
/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

#include "mozmemory.h"
#include "gtest/gtest.h"

// We want to ensure that various functions are hooked properly and that
// allocations are getting routed through jemalloc.  The strategy
// pursued below relies on jemalloc_info_ptr knowing about the pointers
// returned by the allocator.  If the function has been hooked correctly,
// then jemalloc_info_ptr returns a TagLiveAlloc tag, or TagUnknown
// otherwise.
// We could also check the hooking of |free| and similar functions: once
// we free() the returned pointer, jemalloc_info_ptr would return a tag
// that is not TagLiveAlloc. However, in the GTests environment, with
// other threads running in the background, it is possible for some of
// them to get a new allocation at the same location we just freed, and
// jemalloc_info_ptr would return a TagLiveAlloc tag.

#define ASSERT_ALLOCATION_HAPPENED(lambda) \
  ASSERT_TRUE(ValidateHookedAllocation(lambda, free));

// We do run the risk of OOM'ing when we allocate something...all we can
// do is try to allocate something so small that OOM'ing is unlikely.
const size_t kAllocAmount = 16;

static bool ValidateHookedAllocation(void* (*aAllocator)(void),
                                     void (*aFreeFunction)(void*)) {
  void* p = aAllocator();

  if (!p) {
    return false;
  }

  jemalloc_ptr_info_t info;
  jemalloc_ptr_info(p, &info);

  // Regardless of whether that call succeeded or failed, we are done with
  // the allocated buffer now.
  aFreeFunction(p);

  return (info.tag == PtrInfoTag::TagLiveAlloc);
}

TEST(AllocReplacement, malloc_check)
{
  ASSERT_ALLOCATION_HAPPENED([] { return malloc(kAllocAmount); });
}

TEST(AllocReplacement, calloc_check)
{
  ASSERT_ALLOCATION_HAPPENED([] { return calloc(1, kAllocAmount); });
}

TEST(AllocReplacement, realloc_check)
{
  ASSERT_ALLOCATION_HAPPENED([] { return realloc(nullptr, kAllocAmount); });
}

#if defined(HAVE_POSIX_MEMALIGN)
TEST(AllocReplacement, posix_memalign_check)
{
  ASSERT_ALLOCATION_HAPPENED([] {
    void* p = nullptr;
    int result = posix_memalign(&p, sizeof(void*), kAllocAmount);
    if (result != 0) {
      return static_cast<void*>(nullptr);
    }
    return p;
  });
}
#endif