public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: sergiodj@redhat.com (Sergio Durigan Junior)
Cc: gdb-patches@sourceware.org (GDB Patches),
	palves@redhat.com (Pedro Alves),
	       gbenson@redhat.com (Gary Benson),
	       sergiodj@redhat.com (Sergio Durigan Junior)
Subject: Re: [PATCH 2/2] Move code to disable ASR to nat/
Date: Fri, 16 Jan 2015 15:39:00 -0000	[thread overview]
Message-ID: <201501161538.t0GFclYf021559@d03av02.boulder.ibm.com> (raw)
In-Reply-To: <1420841943-24290-3-git-send-email-sergiodj@redhat.com> from "Sergio Durigan Junior" at Jan 09, 2015 05:19:03 PM

Sergio Durigan Junior wrote:

> This patch moves the shared code present on
> gdb/linux-nat.c:linux_nat_create_inferior and
> gdb/gdbserver/linux-low.c:linux_create_inferior to
> nat/linux-personality.c.  This code is responsible for disabling
> address space randomization based on user setting, and using
> <sys/personality.h> to do that.  I decided to put the prototype of the
> maybe_disable_address_space_randomization on nat/linux-osdata.h
> because it seemed the best place to put it.

This breaks building on my RHEL 5 machine:

/home/uweigand/dailybuild/spu-tc-2015-01-15/binutils-gdb-head/binutils-gdb/gdb/nat/linux-personality.c: In function 'maybe_disable_address_space_randomization':
/home/uweigand/dailybuild/spu-tc-2015-01-15/binutils-gdb-head/binutils-gdb/gdb/nat/linux-personality.c:80: error: 'ADDR_NO_RANDOMIZE' undeclared (first use in this function)
/home/uweigand/dailybuild/spu-tc-2015-01-15/binutils-gdb-head/binutils-gdb/gdb/nat/linux-personality.c:80: error: (Each undeclared identifier is reported only once
/home/uweigand/dailybuild/spu-tc-2015-01-15/binutils-gdb-head/binutils-gdb/gdb/nat/linux-personality.c:80: error: for each function it appears in.)

It looks like this is because you replaced:
> -# if !HAVE_DECL_ADDR_NO_RANDOMIZE
by:
> +# ifndef HAVE_DECL_ADDR_NO_RANDOMIZE

but config.h on my machine without ADDR_NO_RANDOMIZE contains:
#define HAVE_DECL_ADDR_NO_RANDOMIZE 0

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com

  parent reply	other threads:[~2015-01-16 15:39 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 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 [this message]
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
2015-01-09 22:19 ` [PATCH 1/2] Move safe_strerror to common/ Sergio Durigan Junior
2015-01-13 16:54   ` Pedro Alves
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

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=201501161538.t0GFclYf021559@d03av02.boulder.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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).