bug-apl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-apl] Possible bug in APL


From: Chris Moller
Subject: [Bug-apl] Possible bug in APL
Date: Sun, 24 Jun 2018 08:29:33 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

Doing some other stuff involving libapl.so, I was running valgrind against my own code when this popped up:


==14122== Source and destination overlap in mempcpy(0x778a9e1, 0x778a9e1, 4)
==14122==    at 0x4C34FF0: mempcpy (vg_replace_strmem.c:1524)
==14122==    by 0x7E06634: realpath@@GLIBC_2.3 (in /usr/lib64/libc-2.27.so)
==14122==    by 0x7441092: LibPaths::search_APL_lib_root() (LibPaths.cc:186)
==14122==    by 0x7441173: LibPaths::init(char const*, bool) (LibPaths.cc:53)
==14122==    by 0x7422B96: init_1(char const*, bool) (Common.cc:77)
==14122==    by 0x7509C09: init_libapl (libapl.cc:435)
==14122==    by 0x4048F9: main (gapl.c:685)


The line in LibPaths.cc is:

unused = realpath(APL_lib_root, APL_lib_root);

which could obviously cause a collision. 

I don't know if this is a real problem or not, but I thought I ought to  mention it to someone.

Chris Moller


reply via email to

[Prev in Thread] Current Thread [Next in Thread]