From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Improve the "thread_step_needed" logic
Date: Mon, 18 Jun 2001 10:37:00 -0000 [thread overview]
Message-ID: <20010618103725.A24473@nevyn.them.org> (raw)
In-Reply-To: <3B2E2839.6E2E4709@cygnus.com>
On Mon, Jun 18, 2001 at 09:11:37AM -0700, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > My apologies. I need to read closer before replying :)
> >
> > I'm assuming that singlestep_breakpoints_inserted_p is zero normally
> > upon entering resume - that only makes sense. In that case, your
> > change preserves the exact behavior I was asking for. I'm going to run
> > it through the testsuite on MIPS/Linux, which I've finally gotten into
> > (almost) functional shape, and let you know if something breaks - I
> > expect that it will not break, though.
>
> Since I do not have a Mips Linux system, I will be
> very interested in your results.
Nothing blew up - in fact, between that and another patch I have my
closest to a successful test run yet. Not great, but:
=== gdb Summary ===
# of expected passes 6603
# of unexpected failures 141
# of unexpected successes 32
# of expected failures 161
# of unresolved testcases 26
# of untested testcases 24
Thanks for your help!
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
next prev parent reply other threads:[~2001-06-18 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 16:35 Michael Snyder
2001-06-15 16:44 ` Daniel Jacobowitz
2001-06-15 18:05 ` Michael Snyder
2001-06-15 18:13 ` Michael Snyder
2001-06-16 11:58 ` Daniel Jacobowitz
2001-06-18 9:11 ` Michael Snyder
2001-06-18 10:37 ` Daniel Jacobowitz [this message]
2001-06-25 17:26 ` Michael Snyder
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=20010618103725.A24473@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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