This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Remaining 7.5 regressions (Re: [ARM, commit, RFA 7.5] Fix HW breakpoints on unaligned addresses)


Joel Brobecker wrote:
> > Joel, would this be OK for the 7.5 branch at this point?
> 
> Sure, as long as a GM is confident about a given change, that is
> good enough for me.

OK, thanks.  I've committed this patch now, as well as two others:
http://sourceware.org/ml/gdb-patches/2012-08/msg00017.html
http://sourceware.org/ml/gdb-patches/2012-08/msg00018.html

> > In general, what's the timeline for 7.5?  I've noticed a couple of
> > other test case regressions when testing the branch on ARM, s390,
> > and Cell ...
> 
> The branch was created on July 17th, and the target date for release
> creation is 2 weeks after that, which would have been today. I thought
> there was still one open issue, but the release page says we're clean
> (except for your issue).

In addition to the failures fixed by the above patches, I'm still seeing:

- Failures in gdb.base/pc-fp.exp on various platforms, as described here:
  http://sourceware.org/ml/gdb-patches/2012-07/msg00823.html
  (just an output formatting issue)

- Failures in gdb.mi/mi-var-rtti.exp on various platforms, see:
  http://sourceware.org/ml/gdb-patches/2012-07/msg00458.html
  (seems to be a bug in the test case)

- Failures in gdb.threads/watchpoint-fork.exp on ARM and PowerPC.
  This looks like a pre-existing bug that hardware watchpoints are not
  handled correctly across forks, which is now exposed since a test
  case for this scenario was added.

- Sporadic timeouts (races?) in gdb.threads/siginfo-threads.exp and
  gdb.threads/ia64-sigill.exp on ARM   (unclear)

- Some new C++ regressions on ARM / s390x (could be compiler issues?)

- Failures in various core file tests on PowerPC (needs investigation)

- Failures in watchpoint.exp on SPU (needs investigation)

- Failures in gdb.server tests on SPU (needs investigation)

- Failures in gdb.threads/siginfo-threads.exp on s390 (needs investigation)

- Failures in gdb.dwarf2/dw2-icc-opaque.exp on SPU and s390 (likewise)

- Testcase harness failures when running a multi-lib configuration:
   ERROR: tcl error sourcing ../../../gdb-7_5/gdb/testsuite/gdb.base/inferior-died.exp.
   ERROR: can't set "seen": variable is array
   ERROR: tcl error sourcing /home/uweigand/fsf/gdb-head/gdb/testsuite/gdb.threads/linux-dp.exp.
   ERROR: can't array set "seen": variable isn't array
  (Invalid re-use of a variable name?)

All these are regressions from 7.4 to 7.5 as far as I can see ...

> The easiest for me would probably to create it on Friday, assuming
> that we don't discover something new by then.

I'll see what I can track down and fix until Friday.  Sorry for starting
my test series a bit late this time ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]