Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nistor Mihail <mihail.nistor@freescale.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb/18947: [aarch64]Step into shared library is very slow.
Date: Thu, 10 Sep 2015 12:11:00 -0000	[thread overview]
Message-ID: <BY2PR0301MB152716775FA837ED530DC6D5E2510@BY2PR0301MB1527.namprd03.prod.outlook.com> (raw)
In-Reply-To: <86613i7b1b.fsf@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 999 bytes --]

Hi Yao,

I have run GDB testsuite for aarch64 and I don't see any regression. 

Best regards,
Mihai

-----Original Message-----
From: Yao Qi [mailto:qiyaoltc@gmail.com] 
Sent: Thursday, September 10, 2015 2:46 PM
To: Nistor Mihail-MNISTOR1 <mihail.nistor@freescale.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/18947: [aarch64]Step into shared library is very slow.

Mihail-Marian Nistor <mihail.nistor@freescale.com> writes:

Hi Mihail-Marian,

> Install gdbarch_skip_solib_resolver on aarch64 GNU/Linux
>
> gdb/ChangeLog:
> 2015-09-10  Mihail-Marian Nistor  <mihail.nistor@freescale.com>
>
> 	PR gdb/18947
> 	* aarch64-linux-tdep.c: (aarch64_linux_init_abi): Install
> 	glibc_skip_solib_resolver as gdbarch_skip_solib_resolver callback.

The patch is OK if you run GDB testsuite for aarch64-linux, and no regressions.  If you don't have an env set up for running GDB testsuite, I can test it for you.

--
Yao (齐尧)
\x16º&Öéj×!zÊÞ¶êç×n}ÛIb²Ö«r\x18\x1dn–­r\x17¬

  reply	other threads:[~2015-09-10 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  9:22 Mihail-Marian Nistor
2015-09-10 11:45 ` Yao Qi
2015-09-10 12:11   ` Nistor Mihail [this message]
2015-09-10 13:56     ` Yao Qi
2015-09-10 14:09       ` Nistor Mihail
2015-09-11 14:26         ` Yao Qi
2015-09-14  9:06           ` Nistor Mihail

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=BY2PR0301MB152716775FA837ED530DC6D5E2510@BY2PR0301MB1527.namprd03.prod.outlook.com \
    --to=mihail.nistor@freescale.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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