Re: [DynInst_API:] Issue about linux-vdso.so.1

[Zifei Tong <soariez@xxxxxxxxx>]

I can confirm with the glibc patch from Fedora [1], my Archlinux
machine runs dyninst without any problem.

[1] http://pkgs.fedoraproject.org/cgit/glibc.git/tree/glibc-fedora-elf-rh737223.patch

--
Zifei Tong


On Wed, Jun 19, 2013 at 1:07 AM, Josh Stone <jistone@xxxxxxxxxx> wrote:
> On 06/18/2013 09:52 AM, Bill Williams wrote:
>> On 06/18/2013 11:33 AM, Matthew LeGendre wrote:
>>>
>>> Zifei,
>>>
>>> I think you've found the right bug.  Dyninst gets all of its library
>>> information from the link maps, and the only way I could imagine this
>>> bug happening is via the vsyscall page being added there.  It doesn't
>>> make a lot of sense for glibc to do this (lots of tools will break), but
>>> oh well.
>>>
>>> It's hard to be sure without a machine to test on, but I believe the
>>> attached patch against Dyninst 8.1.2 would fix the problem.
>>>
>>>
>>> Bill,
>>>
>>> Does the batlab have any machines with a new enough glibc that would
>>> reproduce this?
>>>
>> This may not be a "new enough" question but a "narrow window" question;
>> the batlab has Fedora 16/17/18 at present. By default, F17 has glibc
>> 2.15-59 and F18 has glibc 2.16-31, and I've not observed this problem on
>> either of those platforms. F16 is glibc2.14.90-24, which also does not
>> exhibit this problem.
>
> Fedora 19 and rawhide are also fine, but note that Fedora has patched
> glibc, as stated in comments 2 and 3:
> http://sourceware.org/bugzilla/show_bug.cgi?id=13097#c2
>
> It would be pretty simple to rpmbuild without that patch, if you want to
> test the issue on your Fedora machines.
> _______________________________________________
> Dyninst-api mailing list
> Dyninst-api@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api