5 This file was taken from the nios2 port of the Linux Kernel.
7 Copyright (c) 2008 Atle Nissestad <atle@nissestad.no>
8 Copyright (c) 2010 Tobias Klauser <tklauser@distanz.ch>
10 This file is licensed under the terms of the GNU General Public License,
14 #include <bits/uClibc_page.h>
16 /* Core file format: The core file is written in such a way that gdb
17 can understand it and provide useful information to the user (under
18 linux we use the 'trad-core' bfd). There are quite a number of
19 obstacles to being able to view the contents of the floating point
20 registers, and until these are solved you will not be able to view the
21 contents of them. Actually, you can read in the core file and look at
22 the contents of the user struct to find out what the floating point
24 The actual file contents are as follows:
25 UPAGE: 1 page consisting of a user struct that tells gdb what is present
26 in the file. Directly after this is a copy of the task_struct, which
27 is currently not used by gdb, but it may come in useful at some point.
28 All of the registers are stored as part of the upage. The upage should
29 always be only one page.
30 DATA: The data area is stored. We use current->end_text to
31 current->brk to pick up all of the user variables, plus any memory
32 that may have been malloced. No attempt is made to determine if a page
33 is demand-zero or if a page is totally unused, we just cover the entire
34 range. All of the addresses are rounded in such a way that an integral
35 number of pages is written.
36 STACK: We need the stack information in order to get a meaningful
37 backtrace. We need to write the data from (esp) to
38 current->start_stack, so we round each of these off in order to be able
39 to write an integer number of pages.
40 The minimum core file size is 3 pages, or 12288 bytes.
43 struct user_nios2fp_struct {
46 /* This is the old layout of "struct pt_regs" as of Linux 1.x, and
47 is still the layout used by user (the new pt_regs doesn't have
49 struct user_regs_struct {
50 long r1,r2,r3,r4,r5,r6,r7,r8;
51 long r9,r10,r11,r12,r13,r14,r15;
52 long r16,r17,r18,r19,r20,r21,r22,r23;
59 long status_extension;
63 /* When the kernel dumps core, it starts by dumping the user struct -
64 this will be used by gdb to figure out where the data and stack segments
65 are within the file, and what virtual addresses to use. */
67 /* We start with the registers, to mimic the way that "memory" is returned
68 from the ptrace(3,...) function. */
69 struct user_regs_struct regs; /* Where the registers are actually stored */
71 /* The rest of this junk is to help gdb figure out what goes where */
72 unsigned long int u_tsize; /* Text segment size (pages). */
73 unsigned long int u_dsize; /* Data segment size (pages). */
74 unsigned long int u_ssize; /* Stack segment size (pages). */
75 unsigned long start_code; /* Starting virtual address of text. */
76 unsigned long start_stack; /* Starting virtual address of stack area.
77 This is actually the bottom of the stack,
78 the top of the stack is always found in the
80 long int signal; /* Signal that caused the core dump. */
81 int reserved; /* No longer used */
82 unsigned long u_ar0; /* Used by gdb to help find the values for */
84 unsigned long magic; /* To uniquely identify a core file */
85 char u_comm[32]; /* User command that was responsible */
88 #define NBPG PAGE_SIZE
90 #define HOST_TEXT_START_ADDR (u.start_code)
91 #define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)