public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: warning: Could not load shared library symbols for linux-vdso.so.1.
Date: Mon, 22 Aug 2016 19:47:00 -0000	[thread overview]
Message-ID: <cb801412-5639-c4e8-e0d1-77f6b8f41a2d@redhat.com> (raw)
In-Reply-To: <868tvpcfhs.fsf@gmail.com>

On 08/22/2016 10:36 AM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
> 
>>
>> If reading the elf out of core memory works, then that means that
>> there must be a load segment that covers it.  So that means we should
>> be able to find a PT_LOAD segment for the vDSO, in the core file.  E.g.,:
>>
> 
> It is a good idea to tell the size of vDSO by a PT_LOAD segment.  I
> can't figure out a case this doesn't work.  Patch is good me.
> 
> Note that I am unable to run the tests on the aarch64 machine where I
> reported the problem, because it is stuck in the kernel upgrade.
> However, I run your patch on other aarch64 machine.  Your patch does
> fixes the fails in vdso-warning.exp.
> 
> Thanks a lot for fixing it in different ways.
> 

Alright, I've filed PR 20515 and then pushed to both master and 7.12.

Thanks,
Pedro Alves

      reply	other threads:[~2016-08-22 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 11:46 Yao Qi
2016-08-11 15:57 ` Pedro Alves
2016-08-12 10:28   ` Yao Qi
2016-08-19  1:05     ` Pedro Alves
2016-08-19  9:59       ` Yao Qi
2016-08-19 10:32         ` Pedro Alves
2016-08-19 11:41           ` Yao Qi
2016-08-19 14:02             ` Pedro Alves
2016-08-22  9:36               ` Yao Qi
2016-08-22 19:47                 ` Pedro Alves [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=cb801412-5639-c4e8-e0d1-77f6b8f41a2d@redhat.com \
    --to=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).