public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>,
	 gdb-patches@sourceware.org,
	 "'Joel Brobecker'" <brobecker@adacore.com>
Subject: Re: [RFA- v2] Remove CANNOT_STEP_HW_WATCHPOINTS related code (was fix for bug 11531)
Date: Mon, 26 Apr 2010 11:26:00 -0000	[thread overview]
Message-ID: <201004261226.38885.pedro@codesourcery.com> (raw)
In-Reply-To: <003c01cae515$41e52290$c5af67b0$@muller@ics-cnrs.unistra.fr>

On Monday 26 April 2010 08:51:18, Pierre Muller wrote:
>   Is this patch OK?

This is going in circles, but, why didn't you remove the macro
definition and the whole comment around it from the nm file?
The goal is remove the whole workaround, so you should remove
that too.  The goal of the exercise is to keep each patch
self-contained.  I know you'll remove the nm file afterwards, but,
let's pretend you wouldn't, or that someone would reject that
patch of yours for some reason we haven't thought of yet --- you'll
still want the macro and the comments around it to, _not_ end up
defined in there after this patch.

On Monday 26 April 2010 08:51:18, Pierre Muller wrote:
>   In that case, the configure.tgt script should probably report 
> that Solaris versions <= 2.7 are not supported anymore.
> This is what I added to configure.tgt below.

...

> -i[34567]86-*-solaris*)
> -       # Target: Solaris x86
> +i[34567]86-*-solaris2.[8-9] )
> +       # Target: Solaris x86, only versions 2.8 and 2.9
> +       # Versions <= 2.7 suffer a bug that was handled in older versions of
> 
> +       # GDB, but that code was removed.

It may still work, provided the user doesn't set watchpoints...
In any case, this won't prevent someone building gdb on such
solaris', because you'll still hit the "i[34567]86-*-*)" case
below (and --enable-targets=all will still build the files you're
skipping anyway), leaving the user with a built, but very crippled
GDB, with no hint where to look at.  I suggest leaving this change out
of the patch and focusing on a single thing at a time, otherwise
we'll never get this done.

-- 
Pedro Alves

  reply	other threads:[~2010-04-26 11:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 16:41 [RFA] Testcase for bug report 11531 Pierre Muller
2010-04-23 17:29 ` Joel Brobecker
2010-04-23 18:16   ` Pedro Alves
2010-04-23 18:25     ` Joel Brobecker
2010-04-24 15:13     ` [RFA- v2] Testcase for bug report 11531 and fix for Solaris Pierre Muller
2010-04-25 13:20       ` Joel Brobecker
2010-04-26 11:24         ` [RFA- v3] " Pierre Muller
2010-04-26 16:49           ` Joel Brobecker
2010-04-26 20:50             ` Pierre Muller
2010-04-25 20:10       ` [RFA- v2] " Pedro Alves
2010-04-26 10:55         ` [RFA- v2] Remove CANNOT_STEP_HW_WATCHPOINTS related code (was fix for bug 11531) Pierre Muller
2010-04-26 11:26           ` Pedro Alves [this message]
2010-04-26 11:50             ` Pierre Muller
2010-04-26 11:56               ` Pedro Alves
2010-04-26 12:03                 ` Pierre Muller
2010-04-26 11:29           ` Mark Kettenis
2010-04-26 11:52             ` Pierre Muller

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=201004261226.38885.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).