File: coredump_single_thread.c

package info (click to toggle)
valgrind 1%3A3.16.1-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 158,568 kB
  • sloc: ansic: 746,130; exp: 26,134; xml: 22,708; asm: 13,570; cpp: 7,691; makefile: 6,177; perl: 5,965; sh: 5,665; javascript: 929
file content (46 lines) | stat: -rw-r--r-- 1,238 bytes parent folder | download | duplicates (6)
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
/* Tests that Valgrind coredump support works correctly by producing
   a core dump analyzable by mdb. */

#include <stdio.h>
#include <sys/types.h>

__attribute__((noinline))
static void inner(void)
{
   /* Set registers to apriori known values. */
   __asm__ __volatile__(
      "movq $0x101, %%rax\n"
      "movq $0x102, %%rbx\n"
      "movq $0x103, %%rcx\n"
      "movq $0x104, %%rdx\n"
      "movq $0x105, %%rsi\n"
      "movq $0x106, %%rdi\n"
      "movq $0x107, %%r8\n"
      "movq $0x108, %%r9\n"
      "movq $0x109, %%r10\n"
      "movq $0x10a, %%r11\n"
      "movq $0x10b, %%r12\n"
      "movq $0x10c, %%r13\n"
      "movq $0x10d, %%r14\n"
      "movq $0x10e, %%r15\n"
      // not %rbp as mdb is then not able to reconstruct stack trace
      "movq $0x10f, %%rsp\n"
      "movq $0x1234, (%%rax)\n"  // should cause SEGV here
      "ud2"                      // should never get here
      : // no output registers
      : // no input registers
      : "memory", "%rax", "%rbx", "%rcx", "%rdx", "%rsi", "%rdi",
        "%r8", "%r9", "%r10", "%r11", "%r12", "%r13", "%r14", "%r15", "%rsp");
}

__attribute__((noinline))
static void outer(void)
{
   inner();
}

int main(int argc, const char *argv[])
{
   outer();
   return 0;
}