Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,  drow@false.org
Subject: Re: Regression
Date: Tue, 10 Feb 2009 19:18:00 -0000	[thread overview]
Message-ID: <200902101918.13308.pedro@codesourcery.com> (raw)
In-Reply-To: <200902101905.37812.pedro@codesourcery.com>

Extended this a bit more:

On Tuesday 10 February 2009 19:05:37, Pedro Alves wrote:
> The part that's breaking the BSDs is the fact that we now
> remove breakpoints from the inferior.

On Tuesday 10 February 2009 18:39:04, Mark Kettenis wrote:
> Indeed.  OpenBSD/i386 (as well as NetBSD, FreeBSD and probably Darwin)
> clears the trace bit before running the signal handler.

We don't see the problem on linux, since there's a stop and
resume *right at the begining* of the signal handler, due to the
single-step entering the signal handler.  GDB happens
to re-install breakpoints in the inferior in that resume.  This
happens *before* the inferior's flow passing by the instruction
where there's a breakpoint at ("break handle_USR1" is installed
after the prologue).

-- 
Pedro Alves


  reply	other threads:[~2009-02-10 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 15:17 Regression Mark Kettenis
2009-02-10 15:27 ` Regression Daniel Jacobowitz
2009-02-10 15:47   ` Regression Mark Kettenis
2009-02-10 16:06     ` Regression Pedro Alves
2009-02-10 16:18       ` Regression Tristan Gingold
2009-02-10 18:00       ` Regression Pedro Alves
2009-02-10 18:40         ` Regression Mark Kettenis
2009-02-10 19:05           ` Regression Pedro Alves
2009-02-10 19:18             ` Pedro Alves [this message]
2009-02-10 19:27               ` Regression Pedro Alves
2009-02-11 15:50                 ` Regression Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2009-02-10 15:14 Regression Mark Kettenis

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=200902101918.13308.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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