This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: Verify AT_ENTRY before using it

From: Daniel Jacobowitz <dan at codesourcery dot com>
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
Cc: gdb-patches at sourceware dot org
Date: Wed, 10 Mar 2010 16:55:24 -0500
Subject: Re: RFC: Verify AT_ENTRY before using it
References: <20100224224913.GA25437@caradoc.them.org> <20100225221620.GA7830@host0.dyn.jankratochvil.net> <20100226211216.GC2630@caradoc.them.org> <20100301200428.GA14079@host0.dyn.jankratochvil.net> <20100308220635.GC2629@caradoc.them.org> <20100310211138.GA11271@host0.dyn.jankratochvil.net>

On Wed, Mar 10, 2010 at 10:11:38PM +0100, Jan Kratochvil wrote:
> Factually I do not understand how the warnings could currently ever be printed
> with the DYNAMIC/ET_DYN check there (or do you run PIEs with gdbserver?).

I haven't tried it myself, but it should work fine to do so.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Re: RFC: Verify AT_ENTRY before using it
  - From: Jan Kratochvil
- Re: RFC: Verify AT_ENTRY before using it
  - From: Daniel Jacobowitz
- Re: RFC: Verify AT_ENTRY before using it
  - From: Jan Kratochvil

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]