1 |
1275 |
phoenix |
#ifndef _X86_64_USER_H
|
2 |
|
|
#define _X86_64_USER_H
|
3 |
|
|
|
4 |
|
|
#include <asm/types.h>
|
5 |
|
|
#include <asm/page.h>
|
6 |
|
|
#include <linux/ptrace.h>
|
7 |
|
|
/* Core file format: The core file is written in such a way that gdb
|
8 |
|
|
can understand it and provide useful information to the user.
|
9 |
|
|
There are quite a number of obstacles to being able to view the
|
10 |
|
|
contents of the floating point registers, and until these are
|
11 |
|
|
solved you will not be able to view the contents of them.
|
12 |
|
|
Actually, you can read in the core file and look at the contents of
|
13 |
|
|
the user struct to find out what the floating point registers
|
14 |
|
|
contain.
|
15 |
|
|
|
16 |
|
|
The actual file contents are as follows:
|
17 |
|
|
UPAGE: 1 page consisting of a user struct that tells gdb what is present
|
18 |
|
|
in the file. Directly after this is a copy of the task_struct, which
|
19 |
|
|
is currently not used by gdb, but it may come in useful at some point.
|
20 |
|
|
All of the registers are stored as part of the upage. The upage should
|
21 |
|
|
always be only one page.
|
22 |
|
|
DATA: The data area is stored. We use current->end_text to
|
23 |
|
|
current->brk to pick up all of the user variables, plus any memory
|
24 |
|
|
that may have been malloced. No attempt is made to determine if a page
|
25 |
|
|
is demand-zero or if a page is totally unused, we just cover the entire
|
26 |
|
|
range. All of the addresses are rounded in such a way that an integral
|
27 |
|
|
number of pages is written.
|
28 |
|
|
STACK: We need the stack information in order to get a meaningful
|
29 |
|
|
backtrace. We need to write the data from (esp) to
|
30 |
|
|
current->start_stack, so we round each of these off in order to be able
|
31 |
|
|
to write an integer number of pages.
|
32 |
|
|
The minimum core file size is 3 pages, or 12288 bytes. */
|
33 |
|
|
|
34 |
|
|
/*
|
35 |
|
|
* Pentium III FXSR, SSE support
|
36 |
|
|
* Gareth Hughes <gareth@valinux.com>, May 2000
|
37 |
|
|
*
|
38 |
|
|
* Provide support for the GDB 5.0+ PTRACE_{GET|SET}FPXREGS requests for
|
39 |
|
|
* interacting with the FXSR-format floating point environment. Floating
|
40 |
|
|
* point data can be accessed in the regular format in the usual manner,
|
41 |
|
|
* and both the standard and SIMD floating point data can be accessed via
|
42 |
|
|
* the new ptrace requests. In either case, changes to the FPU environment
|
43 |
|
|
* will be reflected in the task's state as expected.
|
44 |
|
|
*
|
45 |
|
|
* x86-64 support by Andi Kleen.
|
46 |
|
|
*/
|
47 |
|
|
|
48 |
|
|
/* This matches the 64bit FXSAVE format as defined by AMD. It is the same
|
49 |
|
|
as the 32bit format defined by Intel, except that the selector:offset pairs for
|
50 |
|
|
data and eip are replaced with flat 64bit pointers. */
|
51 |
|
|
struct user_i387_struct {
|
52 |
|
|
unsigned short cwd;
|
53 |
|
|
unsigned short swd;
|
54 |
|
|
unsigned short twd; /* Note this is not the same as the 32bit/x87/FSAVE twd */
|
55 |
|
|
unsigned short fop;
|
56 |
|
|
__u64 rip;
|
57 |
|
|
__u64 rdp;
|
58 |
|
|
__u32 mxcsr;
|
59 |
|
|
__u32 mxcsr_mask;
|
60 |
|
|
__u32 st_space[32]; /* 8*16 bytes for each FP-reg = 128 bytes */
|
61 |
|
|
__u32 xmm_space[64]; /* 16*16 bytes for each XMM-reg = 256 bytes */
|
62 |
|
|
__u32 padding[24];
|
63 |
|
|
};
|
64 |
|
|
|
65 |
|
|
/*
|
66 |
|
|
* Segment register layout in coredumps.
|
67 |
|
|
*/
|
68 |
|
|
struct user_regs_struct {
|
69 |
|
|
unsigned long r15,r14,r13,r12,rbp,rbx,r11,r10;
|
70 |
|
|
unsigned long r9,r8,rax,rcx,rdx,rsi,rdi,orig_rax;
|
71 |
|
|
unsigned long rip,cs,eflags;
|
72 |
|
|
unsigned long rsp,ss;
|
73 |
|
|
unsigned long fs_base, gs_base;
|
74 |
|
|
unsigned long ds,es,fs,gs;
|
75 |
|
|
};
|
76 |
|
|
|
77 |
|
|
/* When the kernel dumps core, it starts by dumping the user struct -
|
78 |
|
|
this will be used by gdb to figure out where the data and stack segments
|
79 |
|
|
are within the file, and what virtual addresses to use. */
|
80 |
|
|
struct user{
|
81 |
|
|
/* We start with the registers, to mimic the way that "memory" is returned
|
82 |
|
|
from the ptrace(3,...) function. */
|
83 |
|
|
struct user_regs_struct regs; /* Where the registers are actually stored */
|
84 |
|
|
/* ptrace does not yet supply these. Someday.... */
|
85 |
|
|
int u_fpvalid; /* True if math co-processor being used. */
|
86 |
|
|
/* for this mess. Not yet used. */
|
87 |
|
|
struct user_i387_struct i387; /* Math Co-processor registers. */
|
88 |
|
|
/* The rest of this junk is to help gdb figure out what goes where */
|
89 |
|
|
unsigned long int u_tsize; /* Text segment size (pages). */
|
90 |
|
|
unsigned long int u_dsize; /* Data segment size (pages). */
|
91 |
|
|
unsigned long int u_ssize; /* Stack segment size (pages). */
|
92 |
|
|
unsigned long start_code; /* Starting virtual address of text. */
|
93 |
|
|
unsigned long start_stack; /* Starting virtual address of stack area.
|
94 |
|
|
This is actually the bottom of the stack,
|
95 |
|
|
the top of the stack is always found in the
|
96 |
|
|
esp register. */
|
97 |
|
|
long int signal; /* Signal that caused the core dump. */
|
98 |
|
|
int reserved; /* No longer used */
|
99 |
|
|
struct user_pt_regs * u_ar0; /* Used by gdb to help find the values for */
|
100 |
|
|
/* the registers. */
|
101 |
|
|
struct user_i387_struct* u_fpstate; /* Math Co-processor pointer. */
|
102 |
|
|
unsigned long magic; /* To uniquely identify a core file */
|
103 |
|
|
char u_comm[32]; /* User command that was responsible */
|
104 |
|
|
unsigned long u_debugreg[8];
|
105 |
|
|
};
|
106 |
|
|
#define NBPG PAGE_SIZE
|
107 |
|
|
#define UPAGES 1
|
108 |
|
|
#define HOST_TEXT_START_ADDR (u.start_code)
|
109 |
|
|
#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
|
110 |
|
|
|
111 |
|
|
#endif /* _X86_64_USER_H */
|