Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>,
	Joel Brobecker <brobecker@adacore.com>,
	       gdb-patches@sourceware.org
Subject: Re: gdb-7.8 branching status (2014-06-04)
Date: Thu, 05 Jun 2014 16:07:00 -0000	[thread overview]
Message-ID: <5390959D.3090600@redhat.com> (raw)
In-Reply-To: <539080E5.9000405@codesourcery.com>

On 06/05/2014 03:38 PM, Yao Qi wrote:
> On 06/05/2014 01:18 AM, Joel Brobecker wrote:
>> Quick update on where we are on branching the gdb-7.8 branch:
> 
> I tested gdb head on both arm-none-eabi and arm-none-linux-gnueabi
> yesterday.  Except gdb.cp/koenig.exp fail, there is no regression.
> However, there are some new fails (compared with 7.7.1), but none of
> them are blockers, IMO.
> 
> New FAIL: default/gdb.sum:gdb.base/hbreak-unmapped.exp: hbreak *0
> New FAIL: default/gdb.sum:gdb.base/hbreak-unmapped.exp: info break shows
> hw breakpoint
> 
> bare metal target isn't consider in this case, and I've proposed here
> https://sourceware.org/ml/gdb-patches/2014-06/msg00074.html

TBC, this is just a test issue, not a GDB bug.  I've followed up now.

> 
> FAIL: gdb.base/async.exp: finish&
> FAIL: gdb.base/async.exp: nexti&
> FAIL: gdb.threads/sigstep-threads.exp: continue
> FAIL: gdb.threads/sigstep-threads.exp: step 2
> FAIL: gdb.stabs/gdb11479.exp: sizeof (*e) in test forced_stabs
> FAIL: gdb.stabs/gdb11479.exp: sizeof (*e) in test2 forced_stabs
> FAIL: gdb.base/jit.exp: PIE: one_jit_test-1: continue to breakpoint:
> break here 2 (the program exited)

None of these ring a bell to me atm.

> I'll take a look.

Thanks.

-- 
Pedro Alves


  reply	other threads:[~2014-06-05 16:07 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   ` gdb-7.8 branching status (2014-06-04) Joel Brobecker
2014-06-05 13:58     ` 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 [this message]
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=5390959D.3090600@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@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