Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] HPUX: Remove (non-useful?) definition of PREPARE_TO_PROCEED
Date: Mon, 26 May 2003 22:03:00 -0000	[thread overview]
Message-ID: <20030526220223.GA32360@nevyn.them.org> (raw)
In-Reply-To: <20030526211558.GH11123@gnat.com>

On Mon, May 26, 2003 at 02:15:58PM -0700, Joel Brobecker wrote:
> Re: http://sources.redhat.com/ml/gdb-patches/2003-05/msg00487.html
> 
> Based on Daniel's hunch, I made the following change, and it tested ok
> on our machine. I get the same set of failures for the threads tests:
> 
>     FAIL: gdb.threads/print-threads.exp: Running threads (fast) (timeout)
>     ERROR: Delete all breakpoints in delete_breakpoints (timeout)
>     FAIL: gdb.threads/print-threads.exp: break thread_function (2) (timeout)
>     FAIL: gdb.threads/print-threads.exp: set var slow = 1 (timeout)
>     FAIL: gdb.threads/print-threads.exp: Running threads (slow) (timeout)
>     ERROR: Delete all breakpoints in delete_breakpoints (timeout)
>     FAIL: gdb.threads/print-threads.exp: break thread_function (3) (timeout)
>     FAIL: gdb.threads/print-threads.exp: set var slow = 1 (2) (timeout)
>     FAIL: gdb.threads/print-threads.exp: break kill (timeout)
>     FAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (timeout)
> 
> In all honesty, I know very little about this, so it was just a
> have-a-look kind of test. But based on the fact that this test confirms
> Daniel's initial suspicion, I would think that this patch is safe to
> apply. Since it will help doing some cleanup....

It won't actually show up in the testsuite.  I'm trying and trying to
remember which bug report I was working on when I developed the
prepare-to-proceed patch in the first place.  Also, removing the
definition means that you'll use default_prepare_to_proceed (which is
essentially useless) instead of the generic_prepare_to_proceed which
I'm proposing we use instead.

> 2003-05-26  J. Brobecker  <brobecker@gnat.com>
> 
>         * config/pa/nm-hppah.h (PREPARE_TO_PROCEED): Remove, no longer needed.
>         * hppa-tdep.c (hppa_prepare_to_proceed): Likewise.
> 
> Shall I commit this patch?
> 
> Thanks, (and Thanks to Daniel for the suggestion)

Would you do me the great favor of retesting with changing
PREPARE_TO_PROCEED to use generic_prepare_to_proceed instead of
hppa_prepare_to_proceed?  And if no one objects in a few days, commit
that.  Then the rest falls out, since you will have removed one of the
two remaining specializations of this method.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-05-26 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 21:16 Joel Brobecker
2003-05-26 22:03 ` Daniel Jacobowitz [this message]
2003-05-26 23:20   ` Joel Brobecker
2003-05-27 14:33     ` Andrew Cagney
2003-06-04 20:55     ` Joel Brobecker

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=20030526220223.GA32360@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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