Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: Regression
Date: Tue, 10 Feb 2009 15:47:00 -0000	[thread overview]
Message-ID: <200902101547.n1AFlMsC025262@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20090210152657.GA27195@caradoc.them.org> (message from Daniel 	Jacobowitz on Tue, 10 Feb 2009 10:26:57 -0500)

> Date: Tue, 10 Feb 2009 10:26:57 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Tue, Feb 10, 2009 at 04:17:08PM +0100, Mark Kettenis wrote:
> > Hi Daniel,
> > 
> > The following commit breaks the signal command on OpenBSD.  Can you
> > please revert it for now?
> 
> I'd rather fix OpenBSD than rebreak Linux.  Could you expand on the
> problem?

I don't quite understand what's happening here, but I get the
following new failure:

FAIL: gdb.base/annota1.exp: send SIGUSR1

and some more fallout from that (and similar failures in annota3.exp).
It seems that if we've just hit a breakpoint and then do "signal
SIGUSR1" we never enter the signal handler or ignore the breakpoint in
the signal handler.

I'm somewhat surprised to hear that the same test doesn't fail on x86
Linux for you.


  reply	other threads:[~2009-02-10 15:47 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   ` Mark Kettenis [this message]
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             ` Regression Pedro Alves
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=200902101547.n1AFlMsC025262@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb@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