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 3/4] Fix hw watchpoints #2: reordered / simultaneously hit

From: Pedro Alves <pedro at codesourcery dot com>
To: gdb-patches at sourceware dot org
Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>
Date: Wed, 18 Nov 2009 11:35:30 +0000
Subject: Re: [patch 3/4] Fix hw watchpoints #2: reordered / simultaneously hit
References: <20091116034156.GD22701@host0.dyn.jankratochvil.net> <20091117001056.GE4557@adacore.com> <20091118100810.GA19118@host0.dyn.jankratochvil.net>

On Wednesday 18 November 2009 10:08:10, Jan Kratochvil wrote:
> > "watchpoint_hit_p" might be simpler?
> 
> While I agree the "_p" suffix matches better the GDB coding style I am still
> curious after the years - what does that "_p" mean? ?Guessing "_present"?

"predicate".








(((

FTR, remote.c names these variables as:

  int stopped_by_watchpoint_p;
  CORE_ADDR watch_data_address;

)))

-- 
Pedro Alves

References:
- [patch 3/4] Fix hw watchpoints #2: reordered / simultaneously hit
  - From: Jan Kratochvil
- Re: [patch 3/4] Fix hw watchpoints #2: reordered / simultaneously hit
  - From: Joel Brobecker
- Re: [patch 3/4] Fix hw watchpoints #2: reordered / simultaneously hit
  - From: Jan Kratochvil

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