Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Pedro Alves <pedro_alves@portugalmail.pt>,
	gdb-patches@sourceware.org,
		"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: hbreak.exp: Test hardware breakpoints
Date: Wed, 26 Sep 2007 15:51:00 -0000	[thread overview]
Message-ID: <20070926155114.GA1306@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0709261531470.23821@perivale.mips.com>

On Wed, Sep 26, 2007 at 03:42:05PM +0100, Maciej W. Rozycki wrote:
> Continuing.
> Couldn't write debug register: No such process.
> (gdb) FAIL: gdb.base/hbreak.exp: run until function breakpoint

Sorry, I forgot to warn you about this :-(  You can't use a native
i686-linux debugger to do this test, because the i686 native debugger
defines target_insert_watchpoint et cetera; that message is coming
from GDB trying to use ptrace, even though it's connected to target
remote.

I'll build a cross debugger and give it a try tonight.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-09-26 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 18:10 Maciej W. Rozycki
2007-09-21 23:01 ` Daniel Jacobowitz
2007-09-24 11:23   ` Maciej W. Rozycki
2007-09-24 11:32     ` Daniel Jacobowitz
2007-09-26 14:03       ` Maciej W. Rozycki
2007-09-26 14:21         ` Daniel Jacobowitz
2007-09-26 14:25           ` Maciej W. Rozycki
2007-09-26 14:29             ` Pedro Alves
2007-09-26 14:57               ` Maciej W. Rozycki
2007-09-26 15:51                 ` Daniel Jacobowitz [this message]
2007-09-27  9:58                   ` Maciej W. Rozycki
2007-09-27 12:08                     ` Daniel Jacobowitz
2007-09-30  1:18         ` Daniel Jacobowitz
2007-10-23 17:10           ` Maciej W. Rozycki
2008-02-27 15:39           ` Maciej W. Rozycki
2008-03-01  4:40             ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070926155114.GA1306@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=pedro_alves@portugalmail.pt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox