Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: "Peter.Schauer" <Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC] if (INNER_THAN (read_sp(), step_sp - 16))
Date: Mon, 25 Jun 2001 18:14:00 -0000	[thread overview]
Message-ID: <3B37E1FA.868719D9@cygnus.com> (raw)
In-Reply-To: <3B37DEEA.8BB876E6@cygnus.com>

Michael Snyder wrote:

> To demonstrate this problem, build the "gdb.base/break.exp" test case
> and load it into GDB.  Set a breakpoint at line 79, the call to
> printf(factorial(atoi("6))).  Now set a breakpoint on the last
> instruction of this line, and attempt a "next".  On my red hat 7.0
> linux system, this causes the inferior to SEGV, because it resumes
> after the breakpoint without decrementing the PC (because it failed
> to recognize that it was at a breakpoint).

Aaaaannnd I picked a bad example.  Your step_sp - 16 code is not the
cause of this segv (in fact this reveals _another_ bug).  Let me see
if I can reconstruct my example (it's been a long week and I did not
take notes).


  reply	other threads:[~2001-06-25 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B2A97C7.52A839FD@cygnus.com>
     [not found] ` <3B2A9EC8.7020106@cygnus.com>
2001-06-15 18:13   ` Michael Snyder
2001-06-16  9:42     ` Andrew Cagney
2001-06-23  2:33 ` Peter.Schauer
2001-06-25 18:04   ` Michael Snyder
2001-06-25 18:14     ` Michael Snyder [this message]
2001-06-27 15:10   ` Michael Snyder
2001-06-29  3:08     ` Peter.Schauer
2001-06-29 14:16       ` Michael Snyder
2001-07-01  5:10         ` Peter.Schauer

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=3B37E1FA.868719D9@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE \
    --cc=gdb-patches@sources.redhat.com \
    /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