Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, kettenis@chello.nl,
	drow@false.org, cagney@gnu.org
Subject: Re: [rfc] sigstep additions
Date: Thu, 12 Aug 2004 17:15:00 -0000	[thread overview]
Message-ID: <411BA485.nail17D1733OZ@mindspring.com> (raw)
In-Reply-To: <411ACED7.5040302@gnu.org>

Andrew Cagney <cagney@gnu.org> wrote:
> I'd like to turn this into an RFA.

The superficial parts are all good.

I'm not qualified to comment on the signal handling innards.

I'll approve it in 24-48 hours, unless Daniel or Mark has an objection
or wants more time for review.  (Not even sure if Mark has an interest
in signal handling).

I tried it in three configurations and got these non-PASS results:

  native i686-pc-linux-gnu with red hat linux 8,
  kernel 2.4.18-14-rh, glibc 2.2.93-5-rh
  gcc 3.3.4, binutils 2.15, -gdwarf-2

    FAIL: gdb.base/sigstep.exp: step breakpoint to handler; performing step
    FAIL: gdb.base/sigstep.exp: next breakpoint to handler; performing next
    FAIL: gdb.base/sigstep.exp: continue breakpoint to handler; performing continue

  native hppa2.0w-hp-hpux11.11, hp ansi c B.11.11.28706.gp

    FAIL: gdb.base/sigstep.exp: step from handler; leave handler
    FAIL: gdb.base/sigstep.exp: stepi from handleri; leave signal trampoline
    FAIL: gdb.base/sigstep.exp: next from handler; leave handler
    FAIL: gdb.base/sigstep.exp: nexti from handleri; leave signal trampoline

  native hppa2.0w-hp-hpux11.11, gcc 3.3.4

    FAIL: gdb.base/sigstep.exp: backtrace for nexti (pattern 2)
    FAIL: gdb.base/sigstep.exp: step from handler; leave handler
    FAIL: gdb.base/sigstep.exp: stepi from handleri; leave signal trampoline
    FAIL: gdb.base/sigstep.exp: next from handler; leave handler
    FAIL: gdb.base/sigstep.exp: nexti from handleri; leave signal trampoline
    FAIL: gdb.base/sigstep.exp: finish from handleri; leave handler
    FAIL: gdb.base/sigstep.exp: return from handleri; leave handler

I can send you gdb.log files if you want to work on it more.  It's okay
with me to have FAILs in the results, as long as the test script is
doing real work (as opposed to bombing out with a compiler error).

Michael C

===

2004-08-10  Andrew Cagney  <cagney@gnu.org>

	* gdb.base/sigstep.exp (breakpoint_to_handler)
	(skip_over_handler, skip_to_handler): New test procedures.
	(advance, advancei): Add a proper prefix, do not use
	rerun_to_main.
	* gdb.base/sigstep.c (main): Change to use an infinite loop.


  reply	other threads:[~2004-08-12 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  0:14 Andrew Cagney
2004-08-12  1:59 ` Andrew Cagney
2004-08-12 17:15   ` Michael Chastain [this message]
2004-08-20 11:02   ` Michael Chastain
2004-08-24 14:29     ` Andrew Cagney
2004-08-24 15:47       ` Michael Chastain
2004-08-25 14:40       ` Michael Chastain
2004-08-25 15:29         ` Andrew Cagney

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=411BA485.nail17D1733OZ@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.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