^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) /* SPDX-License-Identifier: GPL-2.0 */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #ifndef _M68K_USER_H
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) #define _M68K_USER_H
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) /* Core file format: The core file is written in such a way that gdb
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) can understand it and provide useful information to the user (under
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) linux we use the 'trad-core' bfd). There are quite a number of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) obstacles to being able to view the contents of the floating point
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) registers, and until these are solved you will not be able to view the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) contents of them. Actually, you can read in the core file and look at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) the contents of the user struct to find out what the floating point
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) registers contain.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) The actual file contents are as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) UPAGE: 1 page consisting of a user struct that tells gdb what is present
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) in the file. Directly after this is a copy of the task_struct, which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) is currently not used by gdb, but it may come in useful at some point.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) All of the registers are stored as part of the upage. The upage should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) always be only one page.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) DATA: The data area is stored. We use current->end_text to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) current->brk to pick up all of the user variables, plus any memory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) that may have been malloced. No attempt is made to determine if a page
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) is demand-zero or if a page is totally unused, we just cover the entire
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) range. All of the addresses are rounded in such a way that an integral
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) number of pages is written.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) STACK: We need the stack information in order to get a meaningful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) backtrace. We need to write the data from (esp) to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) current->start_stack, so we round each of these off in order to be able
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) to write an integer number of pages.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) The minimum core file size is 3 pages, or 12288 bytes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) struct user_m68kfp_struct {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) unsigned long fpregs[8*3]; /* fp0-fp7 registers */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) unsigned long fpcntl[3]; /* fp control regs */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) /* This is the old layout of "struct pt_regs" as of Linux 1.x, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) is still the layout used by user (the new pt_regs doesn't have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) all registers). */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) struct user_regs_struct {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) long d1,d2,d3,d4,d5,d6,d7;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) long a0,a1,a2,a3,a4,a5,a6;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) long d0;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) long usp;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) long orig_d0;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) short stkadj;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) short sr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) long pc;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) short fmtvec;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) short __fill;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) /* When the kernel dumps core, it starts by dumping the user struct -
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) this will be used by gdb to figure out where the data and stack segments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) are within the file, and what virtual addresses to use. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) struct user{
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) /* We start with the registers, to mimic the way that "memory" is returned
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) from the ptrace(3,...) function. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) struct user_regs_struct regs; /* Where the registers are actually stored */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) /* ptrace does not yet supply these. Someday.... */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) int u_fpvalid; /* True if math co-processor being used. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) /* for this mess. Not yet used. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) struct user_m68kfp_struct m68kfp; /* Math Co-processor registers. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) /* The rest of this junk is to help gdb figure out what goes where */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) unsigned long int u_tsize; /* Text segment size (pages). */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) unsigned long int u_dsize; /* Data segment size (pages). */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) unsigned long int u_ssize; /* Stack segment size (pages). */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) unsigned long start_code; /* Starting virtual address of text. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) unsigned long start_stack; /* Starting virtual address of stack area.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) This is actually the bottom of the stack,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) the top of the stack is always found in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) esp register. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) long int signal; /* Signal that caused the core dump. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) int reserved; /* No longer used */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) unsigned long u_ar0; /* Used by gdb to help find the values for */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) /* the registers. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) struct user_m68kfp_struct* u_fpstate; /* Math Co-processor pointer. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) unsigned long magic; /* To uniquely identify a core file */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) char u_comm[32]; /* User command that was responsible */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) #define NBPG 4096
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) #define UPAGES 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) #define HOST_TEXT_START_ADDR (u.start_code)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) #define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) #endif