yann@1625: copied from kernel as it is sanitized now yann@1625: yann@1625: diff -durN glibc-2.10.1.orig/glibc-ports-2.10.1/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.10.1/glibc-ports-2.10.1/sysdeps/unix/sysv/linux/m68k/sys/user.h yann@1625: --- glibc-2.10.1.orig/glibc-ports-2.10.1/sysdeps/unix/sysv/linux/m68k/sys/user.h 2009-05-16 10:36:20.000000000 +0200 yann@1625: +++ glibc-2.10.1/glibc-ports-2.10.1/sysdeps/unix/sysv/linux/m68k/sys/user.h 2009-11-13 00:50:31.000000000 +0100 yann@1625: @@ -1,3 +1,90 @@ yann@1625: +#ifndef _SYS_USER_H yann@1625: +#define _SYS_USER_H yann@1625: + yann@1625: +/* Core file format: The core file is written in such a way that gdb yann@1625: + can understand it and provide useful information to the user (under yann@1625: + linux we use the 'trad-core' bfd). There are quite a number of yann@1625: + obstacles to being able to view the contents of the floating point yann@1625: + registers, and until these are solved you will not be able to view the yann@1625: + contents of them. Actually, you can read in the core file and look at yann@1625: + the contents of the user struct to find out what the floating point yann@1625: + registers contain. yann@1625: + The actual file contents are as follows: yann@1625: + UPAGE: 1 page consisting of a user struct that tells gdb what is present yann@1625: + in the file. Directly after this is a copy of the task_struct, which yann@1625: + is currently not used by gdb, but it may come in useful at some point. yann@1625: + All of the registers are stored as part of the upage. The upage should yann@1625: + always be only one page. yann@1625: + DATA: The data area is stored. We use current->end_text to yann@1625: + current->brk to pick up all of the user variables, plus any memory yann@1625: + that may have been malloced. No attempt is made to determine if a page yann@1625: + is demand-zero or if a page is totally unused, we just cover the entire yann@1625: + range. All of the addresses are rounded in such a way that an integral yann@1625: + number of pages is written. yann@1625: + STACK: We need the stack information in order to get a meaningful yann@1625: + backtrace. We need to write the data from (esp) to yann@1625: + current->start_stack, so we round each of these off in order to be able yann@1625: + to write an integer number of pages. yann@1625: + The minimum core file size is 3 pages, or 12288 bytes. yann@1625: +*/ yann@1625: + yann@1625: +struct user_m68kfp_struct { yann@1625: + unsigned long fpregs[8*3]; /* fp0-fp7 registers */ yann@1625: + unsigned long fpcntl[3]; /* fp control regs */ yann@1625: +}; yann@1625: + yann@1625: +/* This is the old layout of "struct pt_regs" as of Linux 1.x, and yann@1625: + is still the layout used by user (the new pt_regs doesn't have yann@1625: + all registers). */ yann@1625: +struct user_regs_struct { yann@1625: + long d1,d2,d3,d4,d5,d6,d7; yann@1625: + long a0,a1,a2,a3,a4,a5,a6; yann@1625: + long d0; yann@1625: + long usp; yann@1625: + long orig_d0; yann@1625: + short stkadj; yann@1625: + short sr; yann@1625: + long pc; yann@1625: + short fmtvec; yann@1625: + short __fill; yann@1625: +}; yann@1625: + yann@1625: + yann@1625: +/* When the kernel dumps core, it starts by dumping the user struct - yann@1625: + this will be used by gdb to figure out where the data and stack segments yann@1625: + are within the file, and what virtual addresses to use. */ yann@1625: +struct user{ yann@1625: +/* We start with the registers, to mimic the way that "memory" is returned yann@1625: + from the ptrace(3,...) function. */ yann@1625: + struct user_regs_struct regs; /* Where the registers are actually stored */ yann@1625: +/* ptrace does not yet supply these. Someday.... */ yann@1625: + int u_fpvalid; /* True if math co-processor being used. */ yann@1625: + /* for this mess. Not yet used. */ yann@1625: + struct user_m68kfp_struct m68kfp; /* Math Co-processor registers. */ yann@1625: +/* The rest of this junk is to help gdb figure out what goes where */ yann@1625: + unsigned long int u_tsize; /* Text segment size (pages). */ yann@1625: + unsigned long int u_dsize; /* Data segment size (pages). */ yann@1625: + unsigned long int u_ssize; /* Stack segment size (pages). */ yann@1625: + unsigned long start_code; /* Starting virtual address of text. */ yann@1625: + unsigned long start_stack; /* Starting virtual address of stack area. yann@1625: + This is actually the bottom of the stack, yann@1625: + the top of the stack is always found in the yann@1625: + esp register. */ yann@1625: + long int signal; /* Signal that caused the core dump. */ yann@1625: + int reserved; /* No longer used */ yann@1625: + struct user_regs_struct *u_ar0; yann@1625: + /* Used by gdb to help find the values for */ yann@1625: + /* the registers. */ yann@1625: + struct user_m68kfp_struct* u_fpstate; /* Math Co-processor pointer. */ yann@1625: + unsigned long magic; /* To uniquely identify a core file */ yann@1625: + char u_comm[32]; /* User command that was responsible */ yann@1625: +}; yann@1625: +#define NBPG 4096 yann@1625: +#define UPAGES 1 yann@1625: +#define HOST_TEXT_START_ADDR (u.start_code) yann@1625: +#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG) yann@1625: + yann@1625: +#endif yann@1625: /* Copyright (C) 2008 Free Software Foundation, Inc. yann@1625: This file is part of the GNU C Library. yann@1625: yann@1625: diff -durN glibc-2.10.1.orig/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.10.1/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h