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: [PATCH] Forbid watchpoint on a constant value

From: Tom Tromey <tromey at redhat dot com>
To: Sergio Durigan Junior <sergiodj at redhat dot com>
Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org
Date: Thu, 27 May 2010 15:24:37 -0600
Subject: Re: [PATCH] Forbid watchpoint on a constant value
References: <201005181418.24324.sergiodj@redhat.com> <201005200210.27056.sergiodj@redhat.com> <20100520152941.GA19950@host0.dyn.jankratochvil.net> <201005201313.02076.sergiodj@redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:

>> > +	case UNOP_LOWER:
>> > +	case UNOP_UPPER:
>> > +	case UNOP_LENGTH:
>> > +	case UNOP_CARD:
>> > +	case UNOP_CHMAX:
>> > +	case UNOP_CHMIN:

Jan> I do not see implemented evaluation of these, also their processing should
Jan> have been probably moved to ... the already deleted Chill support files.

Sergio> Likewise.

I think the best thing to do is, if you run into some object (function,
variable, constant, type) that is truly unused in gdb, then submit a
separate patch to remove all remaining mentions of it.

Tom

References:
- [PATCH] Forbid watchpoint on a constant value
  - From: Sergio Durigan Junior
- Re: [PATCH] Forbid watchpoint on a constant value
  - From: Sergio Durigan Junior
- Re: [PATCH] Forbid watchpoint on a constant value
  - From: Jan Kratochvil
- Re: [PATCH] Forbid watchpoint on a constant value
  - From: Sergio Durigan Junior

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