From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: Add (extensive) hardware breakpoint testing
Date: Fri, 11 Nov 2011 17:43:00 -0000 [thread overview]
Message-ID: <20111111174247.GF5390@adacore.com> (raw)
In-Reply-To: <CADPb22Qe6G76gDRkVtXhzOhR0w+3VsC9=-eHt-aM=1w8+V7qPg@mail.gmail.com>
> > Â The consistency of failures between i686-linux-gnu and i686-mingw makes
> > me fairly sure that's a bug in x86 support in GDB of some sort rather than
> > a problem with my setup -- is that a known bug?
>
> OOC, have you tried amd64-linux?
> {i386,amd64}-linux are important enough targets that I think this
> should be fixed for 7.4. Joel?
I think we should look at the context as well before making a decision:
- Is that a regression? If it's been like that in previous versions,
then maybe it's OK for it to fail for another version...
- Are hardware breakpoints used much? Probably by the people who
debug programs in ROM(/flash?).
We should probably try to investigate the problem quickly and determine
the extent of the problem. If we think we should fix that for 7.4, and
someone is willing to take responsibility for it, then let's make it
a high priority item on our list, and not release 7.4 without the fix.
--
Joel
next prev parent reply other threads:[~2011-11-11 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 12:13 Maciej W. Rozycki
2011-11-11 17:08 ` Doug Evans
2011-11-11 17:43 ` Joel Brobecker [this message]
2011-11-11 18:59 ` Maciej W. Rozycki
2011-11-12 0:08 ` Pedro Alves
2011-11-14 13:18 ` Maciej W. Rozycki
2011-11-11 20:12 ` Maciej W. Rozycki
2011-12-08 15:33 ` Maciej W. Rozycki
2012-02-27 21:30 ` Ping: " Maciej W. Rozycki
2012-02-28 17:27 ` Pedro Alves
2012-02-28 19:49 ` Maciej W. Rozycki
2012-03-01 11:42 ` Pedro Alves
2012-03-01 21:02 ` Maciej W. Rozycki
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=20111111174247.GF5390@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@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