Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: Teach gdbserver to step over internal breakpoints
Date: Wed, 24 Mar 2010 12:13:00 -0000	[thread overview]
Message-ID: <201003241213.31420.pedro@codesourcery.com> (raw)
In-Reply-To: <201003240005.38983.pedro@codesourcery.com>

On Wednesday 24 March 2010 00:05:38, Pedro Alves wrote:
> I've now tested this on arm-none-linux-gnueabi,
> and there were no regressions.  

I busted this.  I forgot to force a thread event
breakpoint to exercise the code paths on ARM.  I redid the testing
overnight, and it revealed a bunch of regressions; it turns out
I trimmed the original patch too much --- there are some needed
missing bits I left behind.  I'm working on fixing this.

> I've also re-tested this
> on x86_64-linux.  It's now checked in.

-- 
Pedro Alves


  reply	other threads:[~2010-03-24 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 18:40 Pedro Alves
2010-03-24  0:05 ` Pedro Alves
2010-03-24 12:13   ` Pedro Alves [this message]
2010-03-24 21:22     ` Pedro Alves
2010-03-24 21:34       ` Pedro Alves
2010-03-24 22:00       ` Pedro Alves

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=201003241213.31420.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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