public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	       GDB Patches <gdb-patches@sourceware.org>
Cc: Gary Benson <gbenson@redhat.com>
Subject: Re: [PATCH 1/2] Move safe_strerror to common/
Date: Tue, 13 Jan 2015 16:54:00 -0000	[thread overview]
Message-ID: <54B54DDA.7070909@redhat.com> (raw)
In-Reply-To: <1420841943-24290-2-git-send-email-sergiodj@redhat.com>

On 01/09/2015 10:19 PM, Sergio Durigan Junior wrote:
> This patch moves safe_strerror from the gdb/{posix,mingw}-hdep.c files
> to the respective common/{posix,mingw}-strerror.c files.  This is a
> preparation for the next patch, which shares a common code (to disable
> address space randomization when creating a new inferior).
> 
> The patch has been regtested on Fedora 20 x86_64, and no regressions
> were found.  I am assuming the MingW modifications are also safe, but
> I have not checked them too deep.

Note, it's "MinGW", capital G.  There are instances in the patch of the typo.

> 


> --- /dev/null
> +++ b/gdb/common/common.host
> @@ -0,0 +1,17 @@
> +# Mapping of configurations into GDB host definitions.  This is
> +# invoked from the autoconf generated configure script.

Copyright header missing.  I don't know why configure.host
doesn't have one.  Seems like an oversight.

> +
> +# This file sets the following shell variables:
> +#  gdb_host_obs			host-specific .o files to include when building GDB
> +#  srv_host_obs			likewise, but when building gdbserver
> +
> +case "${host}" in
> +
> +i[34567]86-*-mingw32*)	gdb_host_obs="mingw-hdep.o mingw-strerror.o"
> +			srv_host_obs="mingw-strerror.o"
> +			;;
> +x86_64-*-mingw*)        gdb_host_obs="mingw-hdep.o mingw-strerror.o"
> +			srv_host_obs="mingw-strerror.o"
> +			;;

You can merge those two cases.  Let's leave gdb-specific details in gdb proper, etc.
That is, make this file set a common-specific variable, like:

 case "${host}" in

 *-mingw*)	common_host_obs=mingw-strerror.o
 		;;
 *)
 		common_host_obs=posix-strerror.o
 		;;
 ecas

And then in configure.ac, do:

 . $srcdir/common/common.host
 gdb_host_obs=$gdb_host_obs $common_host_obs

Thanks,
Pedro Alves

  reply	other threads:[~2015-01-13 16:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 22:19 [PATCH 0/2] Share code to disable ASR between GDB and gdbserver Sergio Durigan Junior
2015-01-09 22:19 ` [PATCH 1/2] Move safe_strerror to common/ Sergio Durigan Junior
2015-01-13 16:54   ` Pedro Alves [this message]
2015-01-13 20:48     ` Sergio Durigan Junior
2015-01-14 11:26       ` Pedro Alves
2015-01-15  7:05         ` Sergio Durigan Junior
2015-01-15  9:02           ` Pedro Alves
2015-01-16  0:04             ` Sergio Durigan Junior
2015-01-09 22:19 ` [PATCH 2/2] Move code to disable ASR to nat/ Sergio Durigan Junior
2015-01-13 17:11   ` Pedro Alves
2015-01-13 20:55     ` Sergio Durigan Junior
2015-01-14 11:32       ` Pedro Alves
2015-01-15  7:06         ` Sergio Durigan Junior
2015-01-16  0:04         ` Sergio Durigan Junior
2015-01-16 15:39   ` Ulrich Weigand
2015-01-16 16:47     ` [PATCH][commit] Fix regression on RHEL-5 systems (was: Re: [PATCH 2/2] Move code to disable ASR to nat/) Sergio Durigan Junior
2015-01-19 19:16       ` Ulrich Weigand

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=54B54DDA.7070909@redhat.com \
    --to=palves@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).