Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Steve Ellcey <sellcey@caviumnetworks.com>
Cc: binutils <binutils@sourceware.org>,
	gdb-patches <gdb-patches@sourceware.org>,
	Yury Norov <ynorov@caviumnetworks.com>,
	Andreas Schwab <schwab@suse.de>,
	"Pinski, Andrew" <Andrew.Pinski@cavium.com>
Subject: Re: [PATCH] Patch 2 of 2 for aarch64 ILP32 support in gdb
Date: Fri, 03 Feb 2017 09:17:00 -0000	[thread overview]
Message-ID: <20170203091726.GC27498@E107787-LIN> (raw)
In-Reply-To: <1486073021.22118.43.camel@caviumnetworks.com>

On 17-02-02 14:03:41, Steve Ellcey wrote:
> OK, the pthread permission problem was the main cause of my LP64
> failures.  I fixed that, ran the standard gdb testsuite on unpatched
> code in parallel mode and got 99 failures.  If I run in sequential mode
> I got 74 failures.  Updating the kernel got me to 72 failures.  Many of
> these are timeouts so I may need to increase that.  If I ignore the
> timeouts I have 39 failures, which is pretty close to the 36 from the
> buildbot testing though the list of what is and is not failing is
> different.

The result looks reasonable now.

> 
> I then ran the testing with 64 bit programs using the patched sources
> and got about the same results as the unpatched sources on my
> machine.  There was one failure that went away (a timeout):
> 
> FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: continue (timeout)
> 
> And two that appeared:
> 
> FAIL: gdb.base/watchpoint.exp: next over buffer set
> FAIL: gdb.base/watchpoint.exp: next over ptr init
> 
> When I tested gdb on ILP32 executables I got 235 failures, only 3 of
> which were timeouts.  So there are definitely some issues there.  One
> thing I noticed is references to ldd.  The ldd I have in my path does
> not understand ILP32 executables so that is probably causing some
> failures.  I will fix that and see what else I can find to explain the
> ILP32 failures.
> 

OK, great!

-- 
Yao (齐尧)


      reply	other threads:[~2017-02-03  9:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  0:20 Steve Ellcey
2017-01-26 14:14 ` Yao Qi
2017-01-27 22:26   ` Steve Ellcey
2017-01-29 22:41     ` Yao Qi
2017-01-31 23:16       ` Steve Ellcey
2017-02-01 22:20         ` Yao Qi
2017-02-01 22:23           ` Yao Qi
2017-02-02  0:27           ` Steve Ellcey
2017-02-02  0:40           ` Steve Ellcey
2017-02-02  9:52             ` Yao Qi
2017-02-02 22:04               ` Steve Ellcey
2017-02-03  9:17                 ` Yao Qi [this message]

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=20170203091726.GC27498@E107787-LIN \
    --to=qiyaoltc@gmail.com \
    --cc=Andrew.Pinski@cavium.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@suse.de \
    --cc=sellcey@caviumnetworks.com \
    --cc=ynorov@caviumnetworks.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