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: How to get remote target to break on memory access (use z-packet)

From: Daniel Jacobowitz <drow at false dot org>
To: gabe at blackfam dot net
Cc: gdb at sourceware dot org
Date: Thu, 21 Aug 2008 13:18:59 -0400
Subject: Re: How to get remote target to break on memory access (use z-packet)
References: <8a15eb2b0808200957g5fd46a96xb2e69ac60074103a@mail.gmail.com> <20080820185226.GA22063@caradoc.them.org> <8a15eb2b0808211011r31bdb8c8ob5fdc91814e2662b@mail.gmail.com>

On Thu, Aug 21, 2008 at 12:11:14PM -0500, Gabe Black wrote:
> > Try building GDB HEAD instead, or building a cross-configured GDB.
> 
> Ok, so it worked when I built the HEAD on Ubuntu, however, it did not
> work and behaved the same as before when I built it using mingw/msys.
> Was the fix implemented platform dependent?

Yes, it looks like no one fixed mingw.

Don't build a native debugger.  Try --target=i386-elf, or i386-linux,
or whatever it is you're connecting to.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- How to get remote target to break on memory access (use z-packet)
  - From: Gabe Black
- Re: How to get remote target to break on memory access (use z-packet)
  - From: Daniel Jacobowitz
- Re: How to get remote target to break on memory access (use z-packet)
  - From: Gabe Black

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