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 18:26:45 -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> <20070112134932.GA21726@nevyn.them.org> <1168625474.29690.22.camel@mathieu>

On Fri, Jan 12, 2007 at 07:11:14PM +0100, mathieu lacage wrote:
> Which leads me to suspect that my current target (x86 linux FC6) does
> not implement this so, the memory region lookup code returns the default
> region all the time which contains an RW attr. Is this expected ?

That is correct.  As I wrote in a reply earlier, this does not apply
to the notion of "read-only" used by Unix VM systems, where the OS
can create a COW copy for us to use.  It's for debugging ROM images.

-- 
Daniel Jacobowitz
CodeSourcery

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
- Re: help string for "break" command
  - From: Daniel Jacobowitz
- Re: 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]