This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Patch 2 of 2 for aarch64 ILP32 support in gdb


On Thu, 2017-02-02 at 09:51 +0000, Yao Qi wrote:
> On 17-02-01 16:39:56, Steve Ellcey wrote:
> > 
> > It looks like I am having a problem with ptrace.  From gdb.log:
> > 
> > Attaching to program: /home/ubuntu/sellcey/gdb-
> > std/obj/binutils/gdb/testsuite/outputs/gdb.base/attach/attach,
> > process 7631
> > ptrace: Operation not permitted.
> Hi Steve,
> This is a common ptrace attach permission issue.  You can
> "echo 0 > /proc/sys/kernel/yama/ptrace_scope" or modify it in some config
> file /etc/sysctl.d/10-ptrace.conf (different distro may have different
> path).


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.

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.

Steve Ellcey
sellcey@cavium.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]