1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/patches/glibc/ports-2.13/330-m68k-sys-user.patch Tue May 03 00:19:56 2011 +0200
1.3 @@ -0,0 +1,97 @@
1.4 +copied from kernel as it is sanitized now
1.5 +
1.6 +diff -durN glibc-2.13.orig/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.13/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h
1.7 +--- glibc-2.13.orig/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h 2009-05-16 10:36:20.000000000 +0200
1.8 ++++ glibc-2.13/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h 2009-11-13 00:50:31.000000000 +0100
1.9 +@@ -1,3 +1,90 @@
1.10 ++#ifndef _SYS_USER_H
1.11 ++#define _SYS_USER_H
1.12 ++
1.13 ++/* Core file format: The core file is written in such a way that gdb
1.14 ++ can understand it and provide useful information to the user (under
1.15 ++ linux we use the 'trad-core' bfd). There are quite a number of
1.16 ++ obstacles to being able to view the contents of the floating point
1.17 ++ registers, and until these are solved you will not be able to view the
1.18 ++ contents of them. Actually, you can read in the core file and look at
1.19 ++ the contents of the user struct to find out what the floating point
1.20 ++ registers contain.
1.21 ++ The actual file contents are as follows:
1.22 ++ UPAGE: 1 page consisting of a user struct that tells gdb what is present
1.23 ++ in the file. Directly after this is a copy of the task_struct, which
1.24 ++ is currently not used by gdb, but it may come in useful at some point.
1.25 ++ All of the registers are stored as part of the upage. The upage should
1.26 ++ always be only one page.
1.27 ++ DATA: The data area is stored. We use current->end_text to
1.28 ++ current->brk to pick up all of the user variables, plus any memory
1.29 ++ that may have been malloced. No attempt is made to determine if a page
1.30 ++ is demand-zero or if a page is totally unused, we just cover the entire
1.31 ++ range. All of the addresses are rounded in such a way that an integral
1.32 ++ number of pages is written.
1.33 ++ STACK: We need the stack information in order to get a meaningful
1.34 ++ backtrace. We need to write the data from (esp) to
1.35 ++ current->start_stack, so we round each of these off in order to be able
1.36 ++ to write an integer number of pages.
1.37 ++ The minimum core file size is 3 pages, or 12288 bytes.
1.38 ++*/
1.39 ++
1.40 ++struct user_m68kfp_struct {
1.41 ++ unsigned long fpregs[8*3]; /* fp0-fp7 registers */
1.42 ++ unsigned long fpcntl[3]; /* fp control regs */
1.43 ++};
1.44 ++
1.45 ++/* This is the old layout of "struct pt_regs" as of Linux 1.x, and
1.46 ++ is still the layout used by user (the new pt_regs doesn't have
1.47 ++ all registers). */
1.48 ++struct user_regs_struct {
1.49 ++ long d1,d2,d3,d4,d5,d6,d7;
1.50 ++ long a0,a1,a2,a3,a4,a5,a6;
1.51 ++ long d0;
1.52 ++ long usp;
1.53 ++ long orig_d0;
1.54 ++ short stkadj;
1.55 ++ short sr;
1.56 ++ long pc;
1.57 ++ short fmtvec;
1.58 ++ short __fill;
1.59 ++};
1.60 ++
1.61 ++
1.62 ++/* When the kernel dumps core, it starts by dumping the user struct -
1.63 ++ this will be used by gdb to figure out where the data and stack segments
1.64 ++ are within the file, and what virtual addresses to use. */
1.65 ++struct user{
1.66 ++/* We start with the registers, to mimic the way that "memory" is returned
1.67 ++ from the ptrace(3,...) function. */
1.68 ++ struct user_regs_struct regs; /* Where the registers are actually stored */
1.69 ++/* ptrace does not yet supply these. Someday.... */
1.70 ++ int u_fpvalid; /* True if math co-processor being used. */
1.71 ++ /* for this mess. Not yet used. */
1.72 ++ struct user_m68kfp_struct m68kfp; /* Math Co-processor registers. */
1.73 ++/* The rest of this junk is to help gdb figure out what goes where */
1.74 ++ unsigned long int u_tsize; /* Text segment size (pages). */
1.75 ++ unsigned long int u_dsize; /* Data segment size (pages). */
1.76 ++ unsigned long int u_ssize; /* Stack segment size (pages). */
1.77 ++ unsigned long start_code; /* Starting virtual address of text. */
1.78 ++ unsigned long start_stack; /* Starting virtual address of stack area.
1.79 ++ This is actually the bottom of the stack,
1.80 ++ the top of the stack is always found in the
1.81 ++ esp register. */
1.82 ++ long int signal; /* Signal that caused the core dump. */
1.83 ++ int reserved; /* No longer used */
1.84 ++ struct user_regs_struct *u_ar0;
1.85 ++ /* Used by gdb to help find the values for */
1.86 ++ /* the registers. */
1.87 ++ struct user_m68kfp_struct* u_fpstate; /* Math Co-processor pointer. */
1.88 ++ unsigned long magic; /* To uniquely identify a core file */
1.89 ++ char u_comm[32]; /* User command that was responsible */
1.90 ++};
1.91 ++#define NBPG 4096
1.92 ++#define UPAGES 1
1.93 ++#define HOST_TEXT_START_ADDR (u.start_code)
1.94 ++#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
1.95 ++
1.96 ++#endif
1.97 + /* Copyright (C) 2008, 2010 Free Software Foundation, Inc.
1.98 + This file is part of the GNU C Library.
1.99 +
1.100 +diff -durN glibc-2.13.orig/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h