Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Bad checkin breaks Linux
Date: Mon, 14 Jan 2002 11:42:00 -0000	[thread overview]
Message-ID: <3C433357.602055C3@redhat.com> (raw)
In-Reply-To: <20020112163246.A1516@lucon.org>

"H . J . Lu" wrote:
> 
> This patch
> 
> http://sources.redhat.com/ml/gdb-patches/2002-01/msg00195.html
> 
> breaks Linux targets which don't use PTRACE_GETFPXREGS. The problem is
> <sys/ptrace.h> has
> 
>   /* Single step the process.
>      This is not supported on all machines.  */
>   PTRACE_SINGLESTEP = 9,
> #define PT_STEP PTRACE_SINGLESTEP
> 
>   /* Get all general purpose registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_GETREGS = 12,
> #define PT_GETREGS PTRACE_GETREGS
> 
>   /* Set all general purpose registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_SETREGS = 13,
> #define PT_SETREGS PTRACE_SETREGS
> 
>   /* Get all floating point registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_GETFPREGS = 14,
> #define PT_GETFPREGS PTRACE_GETFPREGS
> 
>   /* Set all floating point registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_SETFPREGS = 15,
> #define PT_SETFPREGS PTRACE_SETFPREGS
> 
>   /* Get all extended floating point registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_GETFPXREGS = 18,
> #define PT_GETFPXREGS PTRACE_GETFPXREGS
> 
>   /* Set all extended floating point registers used by a processes.
>      This is not supported on all machines.  */
>    PTRACE_SETFPXREGS = 19,
> #define PT_SETFPXREGS PTRACE_SETFPXREGS
> 
> You can't assume you can use PTRACE_GETFPXREGS if it is defined. Due
> to that change, gdb won't build on Linux/mips. 

Well, that's kind of bogus!  ;-(  
Seems to me that HAVE_PTRACE_GETFPXREGS should mean that 
we have ptrace_getfpxregs.  Maybe MIPS should not define
it if it doesn't use it.

OK, I don't see how to resolve this easily -- I'll just
remove the fpxregs from the gcore file for now (so that
it will build for mips).


> I am afraid the current
> gdb from CVS may be broken even without that patch:
> 
> # gcc -c -g -O2    -I. -I/home/hjl/work/gnu/src/gdb/gdb/gdb -I/home/hjl/work/gnu/src/gdb/gdb/gdb/config -DHAVE_CONFIG_H -I/home/hjl/work/gnu/src/gdb/gdb/gdb/../include/opcode -I/home/hjl/work/gnu/src/gdb/gdb/gdb/../readline/.. -I../bfd -I/home/hjl/work/gnu/src/gdb/gdb/gdb/../bfd -I/home/hjl/work/gnu/src/gdb/gdb/gdb/../include -I../intl -I/home/hjl/work/gnu/src/gdb/gdb/gdb/../intl  -DMI_OUT=1 -DUI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized  /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c
> /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c: In function
> `enable_thread_event_reporting':
> /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c:398: warning: cast from pointer to integer of different size
> /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c:411: warning: cast from pointer to integer of different size
> /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c: In function `thread_db_store_registers':
> /home/hjl/work/gnu/src/gdb/gdb/gdb/thread-db.c:843: warning: passing arg 2 of pointer to function from incompatible pointer type


Check the comment in gdb_proc_service.h (search for "Fix-up some broken
systems"), and see if you may need to define PRFPREGSET_T_BROKEN.

Michael


  parent reply	other threads:[~2002-01-14 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-12 16:32 H . J . Lu
2002-01-14  8:39 ` Elena Zannoni
2002-01-14 11:42 ` Michael Snyder [this message]
2002-01-14 14:47   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C433357.602055C3@redhat.com \
    --to=msnyder@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hjl@lucon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox