Re: GDB 6.2

Re: GDB 6.2

[Michael Elizabeth Chastain]

drow> 1677 is fixed by Bob's patch (not sure if he's checked it in yet).
drow> I have no reason to think that manythreads.exp is fixed, though.

Daniel's right, as usual.

Also there are some hppa-hpux regressions.  I've filed only one PR so
far, gdb/1692.  Jeff J updated the code in bpstat_stop_status so I have
to run another spin.  It might be fixed.  It might not.

That's all the things I know about:

  1650  manythreads, waiting for investigation (daniel j)
  1677  symtab fullname, waiting for patch commit + retest (michael c)
  1692  hpux watchpoint, waiting for retest (michael c)
  about 15 more unanalyzed hppa-hpux testsuite regressions (michael c)

Michael C

GDB 6.2

[Andrew Cagney]

Michael wrote:
> native i686-pc-linux-gnu has two regressions from gdb 6.1 to gdb HEAD.
> 
>   gdb/1650  manythreads.exp
>   gdb/1677  [regression] selftest.exp, crash in lookup_symtab
> 
> 1677 is probably easy to fix.  1650 looks significantly deeper.
> The problem with 1650 is that gdb HEAD randomly gets internal errors,
> but gdb 6.1 does not, on the same test script.

I suspect that these are both fixed?

Jim, Daniel, where do we stand with the ICU code?

Andrew

Re: GDB 6.2

[Daniel Jacobowitz]

On Tue, Jun 29, 2004 at 11:30:19AM -0400, Andrew Cagney wrote:
> Michael wrote:
> >native i686-pc-linux-gnu has two regressions from gdb 6.1 to gdb HEAD.
> >
> >  gdb/1650  manythreads.exp
> >  gdb/1677  [regression] selftest.exp, crash in lookup_symtab
> >
> >1677 is probably easy to fix.  1650 looks significantly deeper.
> >The problem with 1650 is that gdb HEAD randomly gets internal errors,
> >but gdb 6.1 does not, on the same test script.
> 
> I suspect that these are both fixed?

1677 is fixed by Bob's patch (not sure if he's checked it in yet).  I
have no reason to think that manythreads.exp is fixed, though.  I
haven't had time to look at it yet.  It's an intermittent failure; it
doesn't seem to show up running the testsuite without load.  For me at
least.

> Jim, Daniel, where do we stand with the ICU code?

There are about four patches left, fairly large.  Last ping was two
weeks ago.

-- 
Daniel Jacobowitz