From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: vladimir@codesourcery.com (Vladimir Prus)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Stop infrun from tracking breakpoint insertion status.
Date: Wed, 28 Nov 2007 22:24:00 -0000 [thread overview]
Message-ID: <200711282224.lASMOb40006226@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200711272155.17999.vladimir@codesourcery.com> from "Vladimir Prus" at Nov 27, 2007 09:55:17 PM
Vladimir Prus wrote:
> The second problem was that breakpoint_inserted_here_p checks for
> both ordinary breakpoints and single step breakpoints (which don't
> go on bp_location_chain). In most cases, it does not matter, but
> in one place the code tries to figure if we're stopped on a single
> step breakpoint or an ordinary one, and surely, breakpoint_inserted_here_p
> returning 1 for both cases was not good.
>
> The attached revision of the patch introduces a separate
> regular_breakpoint_inserted_here_p function. No regressions on
> either x86 or arm-linux. OK?
I've tested this on powerpc-ibm-aix5.3.0.0 as well, no regressions.
> * breakpoint.h (regular_breakpoint_inserted_here_p): New
> declaration.
> * breakpoint.c (regular_breakpoint_inserted_here_p): New.
> (breakpoint_inserted_here_p): Use
> regular_breakpoint_inserted_here_p.
> * infrun.c (breakpoints_inserted): Remove.
> (resume): Don't check for breakpoints_inserted before
> remove_hw_watchpoints. Use breakpoint_inserted_here_p.
> (proceed, init_wait_for_inferior): Don't set breakpoints_inserted.
> (handle_inferior_event): Don't use breakpoints_inserted.
> Use breakpoints_meant_to_be_inserted and
> breakpoints_inserted_here_p.
> (insert_step_resume_breakpoint_at_sal, keep_going): Use
> breakpoints_meant_to_be_inserted. Don't set breakpoints_inserted.
> (normal_stop): Don't check for breakpoints_inserted. Don't
> set breakpoints_inserted.
> (keep_going): Don't check for breakpoints_inserted.
> (insert_step_resume_breakpoint_at_sal): Don't insert
> breakpoints
This is OK.
> /* Remove breakpoints, SOLIB_ADD might adjust
> breakpoint addresses via breakpoint_re_set. */
> - breakpoints_were_inserted = breakpoints_inserted;
"breakpoints_were_inserted" is now unused, could you please remove
the variable definition as well?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-28 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 11:41 Vladimir Prus
2007-11-19 11:39 ` Ulrich Weigand
2007-11-19 17:00 ` Vladimir Prus
2007-11-20 20:48 ` Vladimir Prus
2007-11-22 0:49 ` Ulrich Weigand
2007-11-22 15:21 ` Vladimir Prus
2007-11-26 15:25 ` Ulrich Weigand
2007-11-27 17:49 ` Vladimir Prus
2007-11-27 18:14 ` Ulrich Weigand
2007-11-28 12:50 ` Vladimir Prus
2007-11-27 18:55 ` Vladimir Prus
2007-11-28 22:24 ` Ulrich Weigand [this message]
2007-11-29 18:46 ` Vladimir Prus
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=200711282224.lASMOb40006226@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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