This is the mail archive of the gdb@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: help string for "break" command

From: Daniel Jacobowitz <drow at false dot org>
To: Mathieu Lacage <Mathieu dot Lacage at sophia dot inria dot fr>
Cc: gdb at sourceware dot org
Date: Fri, 12 Jan 2007 08:49:33 -0500
Subject: Re: help string for "break" command
References: <1168602087.2789.35.camel@garfield.inria.fr> <1168606081.2789.38.camel@garfield.inria.fr> <1168609517.2789.47.camel@garfield.inria.fr>

On Fri, Jan 12, 2007 at 02:45:16PM +0100, Mathieu Lacage wrote:
> Am I right in assuming that the gdb command "break" places exclusively
> so-called software-breakpoints while the command "hbreak" places a
> hardware-breakpoint (I am not sure I have figured out the details of the
> logic in gdb/breakpoint.c) ? 

Not 100%.  CVS versions of GDB will use hardware breakpoints
automatically if you try to set them in truly read-only memory.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: help string for "break" command
  - From: Mathieu Lacage
- Re: help string for "break" command
  - From: mathieu lacage

References:
- placing a breakpoint at a physical address on x86 with gdb
  - From: Mathieu Lacage
- Re: placing a breakpoint at a physical address on x86 with gdb
  - From: Mathieu Lacage
- help string for "break" command
  - From: Mathieu Lacage

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