[ANNOUNCEMENT] GDB 6.8 release process created!

Mirror of the gdb mailing list
 help / color / mirror / Atom feed

* [ANNOUNCEMENT] GDB 6.8 release process created!
@ 2008-02-29 18:55 Joel Brobecker
  2008-02-29 22:25 ` Thiago Jung Bauermann
  2008-03-01  9:47 ` Eli Zaretskii
  0 siblings, 2 replies; 10+ messages in thread
From: Joel Brobecker @ 2008-02-29 18:55 UTC (permalink / raw)
  To: gdb

Hello,

A quick message to announce that the GDB 6.8 branch has just been created.

The prerelease snapshots will be available at:

    ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.bz2

The sources are also accessible via CVS:

    cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co -r gdb_6_8-branch gdb

This announcement has also been posted on the GDB web site at:

    http://www.sourceware.org/gdb/

Cheers,
-- 
Joel


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-02-29 18:55 [ANNOUNCEMENT] GDB 6.8 release process created! Joel Brobecker
@ 2008-02-29 22:25 ` Thiago Jung Bauermann
  2008-03-01  0:20   ` Joel Brobecker
  2008-03-01  9:47 ` Eli Zaretskii
  1 sibling, 1 reply; 10+ messages in thread
From: Thiago Jung Bauermann @ 2008-02-29 22:25 UTC (permalink / raw)
  To: Joel Brobecker; +Cc: gdb ml

Hi,

On Fri, 2008-02-29 at 10:35 -0800, Joel Brobecker wrote:
> A quick message to announce that the GDB 6.8 branch has just been created.

I just noticed that gdb/gdbserver/linux-ppc64-low.c is missing in the
branch. gdbserver doesn't compile on Power systems because of that.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-02-29 22:25 ` Thiago Jung Bauermann
@ 2008-03-01  0:20   ` Joel Brobecker
  2008-03-01  1:16     ` Daniel Jacobowitz
  2008-03-03 17:30     ` Thiago Jung Bauermann
  0 siblings, 2 replies; 10+ messages in thread
From: Joel Brobecker @ 2008-03-01  0:20 UTC (permalink / raw)
  To: Thiago Jung Bauermann; +Cc: gdb ml

Hi Thiago,

> I just noticed that gdb/gdbserver/linux-ppc64-low.c is missing in the
> branch. gdbserver doesn't compile on Power systems because of that.

Thanks for letting me know. So far, I don't understand how this could
have happened. I did the following command (from sourceware):

    % cvs -f -d /cvs/src rtag \
      -D "2008-02-26 10:00-gmt" gdb_6_8-2008-02-26-branchpoint gdb

I have saved the output from this command, stdout and stderr,
and no error was ever printed. And yet, the file was never tagged.
And since the branch is created from the branch-point, it never
made it to the branch.

I double-checked that no other file was missing. So I tagged it, and
then added to the branch.

-- 
Joel

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-01  0:20   ` Joel Brobecker
@ 2008-03-01  1:16     ` Daniel Jacobowitz
  2008-03-03 17:30     ` Thiago Jung Bauermann
  1 sibling, 0 replies; 10+ messages in thread
From: Daniel Jacobowitz @ 2008-03-01  1:16 UTC (permalink / raw)
  To: Joel Brobecker; +Cc: Thiago Jung Bauermann, gdb ml

On Fri, Feb 29, 2008 at 04:19:57PM -0800, Joel Brobecker wrote:
> Hi Thiago,
> 
> > I just noticed that gdb/gdbserver/linux-ppc64-low.c is missing in the
> > branch. gdbserver doesn't compile on Power systems because of that.
> 
> Thanks for letting me know. So far, I don't understand how this could
> have happened. I did the following command (from sourceware):
> 
>     % cvs -f -d /cvs/src rtag \
>       -D "2008-02-26 10:00-gmt" gdb_6_8-2008-02-26-branchpoint gdb

This is probably CVS breaking, but I can tell you the cause if you
haven't noticed it - Ulrich deleted the file on HEAD after the
branchpoint.  It's probably a quirk of -D, which has never been one of
CVS's strong points.

-- 
Daniel Jacobowitz
CodeSourcery


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-01  0:20   ` Joel Brobecker
  2008-03-01  1:16     ` Daniel Jacobowitz
@ 2008-03-03 17:30     ` Thiago Jung Bauermann
  1 sibling, 0 replies; 10+ messages in thread
From: Thiago Jung Bauermann @ 2008-03-03 17:30 UTC (permalink / raw)
  To: Joel Brobecker; +Cc: gdb ml

On Fri, 2008-02-29 at 16:19 -0800, Joel Brobecker wrote:
> I double-checked that no other file was missing. So I tagged it, and
> then added to the branch.

Thanks! All is well now when building on Power.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-02-29 18:55 [ANNOUNCEMENT] GDB 6.8 release process created! Joel Brobecker
  2008-02-29 22:25 ` Thiago Jung Bauermann
@ 2008-03-01  9:47 ` Eli Zaretskii
  2008-03-01 22:21   ` Nick Roberts
  1 sibling, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2008-03-01  9:47 UTC (permalink / raw)
  To: gdb

> Date: Fri, 29 Feb 2008 10:35:23 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> 
> A quick message to announce that the GDB 6.8 branch has just been created.
> 
> The prerelease snapshots will be available at:
> 
>     ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.bz2
> 

FWIW, I've built this prerelease on this machine:

  Linux fencepost 2.6.16.29-xen #1 SMP Wed Dec 6 07:32:36 EST 2006 x86_64 GNU/Linux

It builds okay, and yields the results below for "make check":

		    === gdb Summary ===

    # of expected passes            11833
    # of unexpected failures        73
    # of unexpected successes       2
    # of expected failures          43
    # of known failures             39
    # of untested testcases         10
    # of unsupported tests          49

If someone wants to know details about some specific test cases, I
have the data available, just holler.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-01  9:47 ` Eli Zaretskii
@ 2008-03-01 22:21   ` Nick Roberts
  2008-03-02  3:59     ` Daniel Jacobowitz
  2008-03-02  4:22     ` Eli Zaretskii
  0 siblings, 2 replies; 10+ messages in thread
From: Nick Roberts @ 2008-03-01 22:21 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: gdb

 > It builds okay, and yields the results below for "make check":
 > 
 > 		    === gdb Summary ===
 > 
 >     # of expected passes            11833
 >     # of unexpected failures        73
 >     # of unexpected successes       2
 >     # of expected failures          43
 >     # of known failures             39
 >     # of untested testcases         10
 >     # of unsupported tests          49
 > 
 > If someone wants to know details about some specific test cases, I
 > have the data available, just holler.

That seems like a lot of failures. Are any of these the ones Vladimir
pointed out?:

        FAIL: gdb.base/annota1.exp: continue to printf
        FAIL: gdb.base/annota1.exp: send SIGUSR1
        FAIL: gdb.base/annota1.exp: signal sent
        FAIL: gdb.cp/annota2.exp: continue to exit
        FAIL: gdb.cp/annota2.exp: watch triggered on a.x

He says:

> JFYI -- I'm not sure we should bother about annotations.

If that's to wind me up - that's fine, I probably can't expect any more,
but I hope it's not GDB policy.

In this particular case, it's not a problem because Emacs doesn't use
frames-invalid annotations - but it does use others.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-01 22:21   ` Nick Roberts
@ 2008-03-02  3:59     ` Daniel Jacobowitz
  2008-03-02  4:24       ` Eli Zaretskii
  2008-03-02  4:22     ` Eli Zaretskii
  1 sibling, 1 reply; 10+ messages in thread
From: Daniel Jacobowitz @ 2008-03-02  3:59 UTC (permalink / raw)
  To: Nick Roberts; +Cc: Eli Zaretskii, gdb

On Sun, Mar 02, 2008 at 11:20:45AM +1300, Nick Roberts wrote:
> That seems like a lot of failures.

Mid-seventies is about typical for my runs.  For instance most of the
Ada tests blow up with current FSF gnat (Joel knows about this, the
AdaCore sources work better).  GPC, if you have it installed, fails a
bunch of Pascal tests.

>         FAIL: gdb.base/annota1.exp: continue to printf
>         FAIL: gdb.base/annota1.exp: send SIGUSR1
>         FAIL: gdb.base/annota1.exp: signal sent
>         FAIL: gdb.cp/annota2.exp: continue to exit
>         FAIL: gdb.cp/annota2.exp: watch triggered on a.x

I fixed these in HEAD right after I was informed of them.  I don't
think either the patch causing them or fixing them has been moved to
the branch.

-- 
Daniel Jacobowitz
CodeSourcery

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-02  3:59     ` Daniel Jacobowitz
@ 2008-03-02  4:24       ` Eli Zaretskii
  0 siblings, 0 replies; 10+ messages in thread
From: Eli Zaretskii @ 2008-03-02  4:24 UTC (permalink / raw)
  To: Daniel Jacobowitz; +Cc: nickrob, gdb

> Date: Sat, 1 Mar 2008 22:59:12 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
> 
> On Sun, Mar 02, 2008 at 11:20:45AM +1300, Nick Roberts wrote:
> > That seems like a lot of failures.
> 
> Mid-seventies is about typical for my runs.  For instance most of the
> Ada tests blow up with current FSF gnat (Joel knows about this, the
> AdaCore sources work better).  GPC, if you have it installed, fails a
> bunch of Pascal tests.

I have neither Gnat nor GPC on that machine, and the respective
failures are not in the test logfiles.

> >         FAIL: gdb.base/annota1.exp: continue to printf
> >         FAIL: gdb.base/annota1.exp: send SIGUSR1
> >         FAIL: gdb.base/annota1.exp: signal sent
> >         FAIL: gdb.cp/annota2.exp: continue to exit
> >         FAIL: gdb.cp/annota2.exp: watch triggered on a.x
> 
> I fixed these in HEAD right after I was informed of them.  I don't
> think either the patch causing them or fixing them has been moved to
> the branch.

I don't see these in the logs, FWIW.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ANNOUNCEMENT] GDB 6.8 release process created!
  2008-03-01 22:21   ` Nick Roberts
  2008-03-02  3:59     ` Daniel Jacobowitz
@ 2008-03-02  4:22     ` Eli Zaretskii
  1 sibling, 0 replies; 10+ messages in thread
From: Eli Zaretskii @ 2008-03-02  4:22 UTC (permalink / raw)
  To: Nick Roberts; +Cc: gdb

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 2 Mar 2008 11:20:45 +1300
> Cc: gdb@sourceware.org
> 
> That seems like a lot of failures. Are any of these the ones Vladimir
> pointed out?:
> 
>         FAIL: gdb.base/annota1.exp: continue to printf
>         FAIL: gdb.base/annota1.exp: send SIGUSR1
>         FAIL: gdb.base/annota1.exp: signal sent
>         FAIL: gdb.cp/annota2.exp: continue to exit
>         FAIL: gdb.cp/annota2.exp: watch triggered on a.x

It doesn't look like that.  I attach below all the FAILs and XFAILs.

--------------------------------------------------------------------
XFAIL: gdb.base/completion.exp: complete 'p "break1.'
FAIL: gdb.base/corefile.exp: accessing mmapped data in core file (mapping address not found in core file)
XFAIL: gdb.base/dbx.exp: func sum
XFAIL: gdb.base/dbx.exp: func print_average
XFAIL: gdb.base/exprs.exp: truncate (void*) 0x00000000ffffffff + 1
XFAIL: gdb.base/exprs.exp: truncate (void*) 0xffffffff00000000 - 1
XFAIL: gdb.base/list.exp: list line 1 with unlimited listsize
XFAIL: gdb.base/list.exp: list filename:function; wrong filename rejected
XFAIL: gdb.base/macscp.exp: executable includes no macro debugging information
KFAIL: gdb.base/printcmds.exp: ptype &*"foo" (PRMS: gdb/538)
KFAIL: gdb.base/radix.exp: print 20.; expect 24; output radix 8 (PRMS: gdb/1715)
KFAIL: gdb.base/radix.exp: print 20.; expect 14; output radix 16 (PRMS: gdb/1715)
FAIL: gdb.base/sigaltstack.exp: finish from catch LEAF (the program exited)
FAIL: gdb.base/sigaltstack.exp: finish to throw INNER
FAIL: gdb.base/sigaltstack.exp: finish to catch INNER
FAIL: gdb.base/sigaltstack.exp: finish from catch INNER
FAIL: gdb.base/sigaltstack.exp: finish to OUTER
FAIL: gdb.base/sigaltstack.exp: finish to catch MAIN
FAIL: gdb.base/sigaltstack.exp: finish to MAIN
FAIL: gdb.base/sigbpt.exp: stepi; stepi out of handler
FAIL: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler
FAIL: gdb.base/sigbpt.exp: stepi bp at segv; stepi out of handler
FAIL: gdb.base/sigbpt.exp: stepi bp before and at segv; stepi out of handler
FAIL: gdb.base/siginfo.exp: step out of handler
KFAIL: gdb.base/signals.exp: override SIGINT (PRMS: gdb/1707)
FAIL: gdb.base/sigstep.exp: step from handler; leave handler
FAIL: gdb.base/sigstep.exp: stepi from handleri; leave handler
FAIL: gdb.base/sigstep.exp: stepi from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: next from handler; leave handler
FAIL: gdb.base/sigstep.exp: nexti from handleri; leave handler
FAIL: gdb.base/sigstep.exp: nexti from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: finish from handleri; leave handler (hit breakpoint again)
FAIL: gdb.base/sigstep.exp: finish from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: return from handleri; leave handler
FAIL: gdb.base/sigstep.exp: return from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: step to handler; resync
FAIL: gdb.base/sigstep.exp: step to handler; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next to handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next to handler; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue to handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue to handler; performing continue (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step to handler entry; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next to handler entry; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue to handler entry; performing continue (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step over handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step over handler; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next over handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next over handler; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue over handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue over handler; performing continue (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler; performing continue (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler entry; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler entry; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler entry; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler entry; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler entry; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler entry; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler entry; performing continue (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, skip handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, skip handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: step on breakpoint, skip handler; performing step (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, skip handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, skip handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: next on breakpoint, skip handler; performing next (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, skip handler; resync (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, skip handler; continue to infinite loop (the program is no longer running)
FAIL: gdb.base/sigstep.exp: continue on breakpoint, skip handler; performing continue (the program is no longer running)
KFAIL: gdb.base/solib-weak.exp: run to breakpoint - lib1 nodebug, lib2 debug, lib1 first (PRMS: gdb/1824)
KFAIL: gdb.base/solib-weak.exp: run to breakpoint - lib1 debug, lib2 nodebug, lib2 first (PRMS: gdb/1824)
KFAIL: gdb.cp/annota2.exp: watch triggered on a.x (PRMS: gdb/38)
KFAIL: gdb.cp/annota3.exp: watch triggered on a.x (PRMS: gdb/38)
FAIL: gdb.cp/arg-reference.exp: No false reference
KFAIL: gdb.cp/classes.exp: ptype obj_with_enum // unrecognized line type 1: PrivEnum priv_enum; (PRMS: gdb/57)
KFAIL: gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42 (PRMS: gdb/1588)
KFAIL: gdb.cp/classes.exp: print ('ClassWithEnum::PrivEnum') 42 (PRMS: gdb/57)
KFAIL: gdb.cp/demangle.exp: lucid: __vtbl__3foo__vt_cc_main_ (PRMS: gdb/945)
KFAIL: gdb.cp/inherit.exp: print g_D.A::a (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: print g_D.A::x (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: print g_E.A::a (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: print g_E.A::x (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: ptype g_D.A::a (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: ptype g_D.A::x (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: ptype g_E.A::a (PRMS: gdb/68)
KFAIL: gdb.cp/inherit.exp: ptype g_E.A::x (PRMS: gdb/68)
KFAIL: gdb.cp/local.exp: ptype InnerLocal::NestedInnerLocal (PRMS: gdb/482)
KFAIL: gdb.cp/namespace.exp: ptype ::C::CClass (PRMS: gdb/1448)
KFAIL: gdb.cp/namespace.exp: ptype ::C::CClass::NestedClass (PRMS: gdb/1448)
KFAIL: gdb.cp/namespace.exp: ptype ::C::NestedClass (PRMS: gdb/1448)
KFAIL: gdb.cp/namespace.exp: ptype ::C::OtherFileClass (PRMS: gdb/1448)
KFAIL: gdb.cp/templates.exp: ptype T5<int> (PRMS: gdb/1111)
KFAIL: gdb.cp/templates.exp: ptype T5<int> (PRMS: gdb/1111)
KFAIL: gdb.cp/templates.exp: constructor breakpoint (PRMS: gdb/1062)
KFAIL: gdb.cp/templates.exp: destructor breakpoint (PRMS: gdb/1112)
KFAIL: gdb.cp/templates.exp: ptype fvpchar (PRMS: gdb/1512)
KFAIL: gdb.cp/templates.exp: print Foo<volatile char *>::foo (PRMS: gdb/931)
KFAIL: gdb.cp/templates.exp: print Foo<volatile char*>::foo (PRMS: gdb/931)
KFAIL: gdb.cp/templates.exp: ptype quxint (PRMS: gdb/1512)
KFAIL: gdb.cp/virtfunc.exp: print pEe->D::vg() (PRMS: gdb/1064)
FAIL: gdb.dwarf2/dw2-ranges.exp: info line func
XFAIL: gdb.mi/mi-break.exp: break-insert -r operation
XFAIL: gdb.mi/mi-break.exp: insert breakpoint with regexp callee2
XFAIL: gdb.mi/mi-break.exp: insert breakpoint with regexp callee
XFAIL: gdb.mi/mi-break.exp: insert breakpoint with regexp .*llee
XFAIL: gdb.mi/mi-break.exp: list of breakpoints
KFAIL: gdb.mi/mi-until.exp: until after while loop (went backwards) (PRMS: gdb/2104)
XFAIL: gdb.mi/mi-var-block.exp: update inner_foo: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi-var-block.exp: evaluate inner_foo: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi-var-block.exp: update foo2: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi-var-block.exp: update foo2 should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi-var-block.exp: update foo should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi-var-child.exp: update all vars psnp->next->long_ptr (and 1.long_ptr) changed
XFAIL: gdb.mi/mi-var-cmd.exp: update all vars: changed FIXME
XFAIL: gdb.mi/mi-var-display.exp: eval variable e
XFAIL: gdb.mi/mi-watch.exp: sw: wp out of scope (2)
XFAIL: gdb.mi/mi2-break.exp: break-insert -r operation
XFAIL: gdb.mi/mi2-break.exp: insert breakpoint with regexp callee2
XFAIL: gdb.mi/mi2-break.exp: insert breakpoint with regexp callee
XFAIL: gdb.mi/mi2-break.exp: insert breakpoint with regexp .*llee
XFAIL: gdb.mi/mi2-break.exp: list of breakpoints
KFAIL: gdb.mi/mi2-console.exp: Hello message (PRMS: gdb/623)
KFAIL: gdb.mi/mi2-until.exp: until after while loop (went backwards) (PRMS: gdb/2104)
XFAIL: gdb.mi/mi2-var-block.exp: update inner_foo: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi2-var-block.exp: evaluate inner_foo: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi2-var-block.exp: update foo2: should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi2-var-block.exp: update foo2 should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi2-var-block.exp: update foo should be out of scope: KNOWN PROBLEM
XFAIL: gdb.mi/mi2-var-child.exp: update all vars psnp->next->long_ptr (and 1.long_ptr) changed
XFAIL: gdb.mi/mi2-var-cmd.exp: update all vars: changed FIXME
XFAIL: gdb.mi/mi2-var-display.exp: eval variable e
XFAIL: gdb.mi/mi2-watch.exp: sw: wp out of scope (2)
KFAIL: gdb.pascal/types.exp: pt 'a simple string' (PRMS: gdb/2326)
XFAIL: gdb.stabs/weird.exp: print struct constant
XFAIL: gdb.stabs/weird.exp: array0 with strange index
XFAIL: gdb.stabs/weird.exp: array1 with strange index
XFAIL: gdb.stabs/weird.exp: whatis pointer_to_int_var
XFAIL: gdb.stabs/weird.exp: whatis intp_var
XFAIL: gdb.stabs/weird.exp: p common0var1
XFAIL: gdb.stabs/weird.exp: p common0var2
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.threads/staticthreads.exp: Continue to main's call of sem_post
FAIL: gdb.threads/staticthreads.exp: handle SIG32 helps
KFAIL: gdb.threads/tls.exp: info address me (PRMS: gdb/1294)


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2008-03-03 17:30 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-29 18:55 [ANNOUNCEMENT] GDB 6.8 release process created! Joel Brobecker
2008-02-29 22:25 ` Thiago Jung Bauermann
2008-03-01  0:20   ` Joel Brobecker
2008-03-01  1:16     ` Daniel Jacobowitz
2008-03-03 17:30     ` Thiago Jung Bauermann
2008-03-01  9:47 ` Eli Zaretskii
2008-03-01 22:21   ` Nick Roberts
2008-03-02  3:59     ` Daniel Jacobowitz
2008-03-02  4:24       ` Eli Zaretskii
2008-03-02  4:22     ` Eli Zaretskii

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox