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] Don't allow setting register in non-innermost frame

From: Tom Tromey <tromey at redhat dot com>
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
Cc: Yao Qi <yao at codesourcery dot com>, Doug Evans <dje at google dot com>, gdb-patches at sourceware dot org
Date: Tue, 11 Sep 2012 11:23:23 -0600
Subject: Re: [RFC] Don't allow setting register in non-innermost frame
References: <1345170040-25959-1-git-send-email-yao@codesourcery.com> <CADPb22SGp-9TaoA3rNi_PJordCuv_bjwFQZiHvfjktHx3Y_krA@mail.gmail.com> <87hartpodt.fsf@fleche.redhat.com> <20120907164544.GA18234@host2.jankratochvil.net> <504D49DA.6070006@codesourcery.com> <87ehm8a3gg.fsf@fleche.redhat.com> <20120911171932.GA23134@host2.jankratochvil.net>

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> I also did not like TYPE_OBJFILE_OWNED too much, I was thinking putting it
Jan> possibly to
Jan> 	evaluate_subexp_standard <BINOP_ASSIGN>
Jan> checking there LHS (left hand side) expression, not the LHS value.

Yeah, I almost mentioned that approach as well.
I agree it would probably be ok; but it also requires checking whether
any language overrides this opcode.

Tom

References:
- Re: [RFC] Don't allow setting register in non-innermost frame
  - From: Jan Kratochvil
- Re: [RFC] Don't allow setting register in non-innermost frame
  - From: Yao Qi
- Re: [RFC] Don't allow setting register in non-innermost frame
  - From: Tom Tromey
- Re: [RFC] Don't allow setting register in non-innermost frame
  - From: Jan Kratochvil

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