https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #10 from Josef Weidendorfer ---
Original Callgrind author here...
Sorry for not checking my old email address for open-source projects obviously
for almost 1 1/2 years... just see this now, as I was checking out callgrind on
recent Ubuntu
https://bugs.kde.org/show_bug.cgi?id=415293
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=415293
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #7 from pcpa ---
Appears to work for me.
I will confirm with the person that pointed out the problem if it works
on their environment, but unlikely to not work.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #6 from Mark Wielaard ---
Created attachment 130439
--> https://bugs.kde.org/attachment.cgi?id=130439=edit
Patch to search/check all possible dl_runtime_resolve variants
I tweaked your patch a little so we detect all variants, all
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #5 from pcpa ---
It should be tricky to figure what version is being used.
Could look into the 'the elf_machine_runtime_setup' function in
sysdeps/${ARCH}/dl-machine.h glibc source.
Sample chunk from rhel7 x86_64 source:
...
if
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #4 from pcpa ---
Created attachment 128770
--> https://bugs.kde.org/attachment.cgi?id=128770=edit
sample_callgrind.tgz
This a reproducer from a Red Hat user.
The repro.sh script works with or without devtoolset installed.
On a example
https://bugs.kde.org/show_bug.cgi?id=415293
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #2 from pcpa ---
Created attachment 126591
--> https://bugs.kde.org/attachment.cgi?id=126591=edit
valgrind-3.14.0-rhbz1784541.patch
This is a suggested patch or possible way to handle the issue.
The user that had the issue now has it
https://bugs.kde.org/show_bug.cgi?id=415293
Julian Seward changed:
What|Removed |Added
CC||josef.weidendor...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #1 from pcpa ---
As an extra note, there are several different _dl_runtime_resolve{EXT}
variants. I believe only one is used in an application, but there are
multiple names.
A possible fix is to use the logic in callgrind/fn.c so that when
11 matches
Mail list logo
