This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: stack-protector guard location

From: Tom Tromey <tromey at redhat dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: Roland McGrath <roland at redhat dot com>, Andrew Pinski <pinskia at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 28 Aug 2009 09:31:41 -0600
Subject: Re: stack-protector guard location
References: <20090827225535.CF70E4050F@magilla.sf.frob.com> <4A971CE3.2060404@redhat.com> <20090828001251.1FC4645B02@magilla.sf.frob.com> <4A9722DB.6000606@redhat.com> <20090828014800.8AE2D45B02@magilla.sf.frob.com> <820B85D5-FB21-4228-A275-8D40564D6144@gmail.com> <20090828020523.3E42645B02@magilla.sf.frob.com> <4A974BE6.8090703@redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "rth" == Richard Henderson <rth@redhat.com> writes:

rth> Even then I'd hope that the debugger returns a user decl before one
rth> that's marked DW_AT_artificial.

I am reasonably sure that current gdb won't do this.

You could introduce a new scope for the artificial variable.
Then if the user happened to use this name it would shadow the
artificial decl.  This doesn't work for parameter names, though.

Tom

References:
- Re: stack-protector guard location
  - From: Richard Henderson
- Re: stack-protector guard location
  - From: Roland McGrath
- Re: stack-protector guard location
  - From: Richard Henderson
- Re: stack-protector guard location
  - From: Roland McGrath
- Re: stack-protector guard location
  - From: Andrew Pinski
- Re: stack-protector guard location
  - From: Roland McGrath
- Re: stack-protector guard location
  - From: Richard Henderson

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