Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.8 branching status (2014-06-04)
Date: Wed, 04 Jun 2014 18:20:00 -0000	[thread overview]
Message-ID: <20140604182038.GX4289@adacore.com> (raw)
In-Reply-To: <538F58DE.7030204@redhat.com>

> I also filed PRs for the gdbserver regressions I had mentioned before.
> 
>  [Bug go/17018] New: XFAIL: gdb.go/hello.exp: Starting string check
>  https://sourceware.org/PR17018
> 
>  [Bug gdb/17019] New: gdb.base/restore.exp failures
>  https://sourceware.org/PR17019
> 
>  [Bug gdb/17020] New: gdb.base/store.exp failures
>  https://sourceware.org/PR17020
> 
>  [Bug gdb/17016] New: XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete
>  https://sourceware.org/PR17016
> 
>  [Bug gdb/17015] New: gdb.trace/collection.exp failures
>  https://sourceware.org/PR17015
> 
>  [Bug gdb/17014] New: gdb.trace/unavailable.exp failures
>  https://sourceware.org/PR17014
> 
> Likely most of those are system/gcc related though.  I'm diffing
> against a gdb.sum from a month ago, and I updated my Fedora in
> the mean time...  Still, it's shame that all these are failing
> on newer systems.
> 
> I'll run the testsuite on my current system against 7.7,
> diff the result against mainline, and update the PRs with
> what I find out.  If they fail on 7.7 as well, they're not
> regressions, so can't be blockers.

Thanks for doing that, Pedro. Let us know when you have the results,
so we know whether we're in the clear or not...

-- 
Joel


  parent reply	other threads:[~2014-06-04 18:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 17:18 Joel Brobecker
2014-06-04 17:35 ` Pedro Alves
2014-06-04 17:46   ` Joel Brobecker
2014-06-04 17:54     ` Pedro Alves
2014-06-04 17:58       ` Pedro Alves
2014-06-04 18:17         ` [RFA] gdbserver crash if the_target->supports_z_point_type is NULL Joel Brobecker
2014-06-04 20:09           ` Pedro Alves
2014-06-04 22:21             ` pushed: " Joel Brobecker
2014-06-04 18:20   ` Joel Brobecker [this message]
2014-06-05 13:58     ` gdb-7.8 branching status (2014-06-04) Pedro Alves
2014-06-05 14:15       ` Keith Seitz
2014-06-05 14:39         ` Keith Seitz
2014-06-05 21:49       ` Joel Brobecker
2014-06-04 18:41 ` Keith Seitz
2014-06-04 22:23   ` Joel Brobecker
2014-06-05 17:26     ` Doug Evans
2014-06-04 23:03 ` Joel Brobecker
2014-06-05 21:03   ` Joel Brobecker
2014-06-06 16:30     ` Pedro Alves
2014-06-05 21:47   ` Joel Brobecker
2014-06-05 14:40 ` Yao Qi
2014-06-05 16:07   ` Pedro Alves
2014-06-05 21:50   ` Joel Brobecker

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=20140604182038.GX4289@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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