[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390498

--- Comment #7 from r...@sc3d.org ---
Sorry, I didn't say that a rebuild fixed it; a Termux script
(termux-elf-cleaner) used to remove some supposedly unneeded stuff from ELF
binaries was found to be the culprit.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[Julian Seward]

https://bugs.kde.org/show_bug.cgi?id=390498

--- Comment #6 from Julian Seward  ---
(In reply to rrt from comment #5)
> I've filed https://github.com/termux/termux-packages/issues/2148

Hi!  I fixed some debuginfo reading stuff for arm64-linux recently
(within the past month) so it might be worth you trying the git
trunk, to see if this still happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390498

--- Comment #5 from r...@sc3d.org ---
I've filed https://github.com/termux/termux-packages/issues/2148

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390498

--- Comment #4 from r...@sc3d.org ---
As I said, it's a stock build. So looks like a problem with the Termux build,
I'll investigate that. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[Tom Hughes]

https://bugs.kde.org/show_bug.cgi?id=390498

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #3 from Tom Hughes  ---
That probably means you have stripped all the unwind information from
vgpreload_memcheck-arm64-linux.so so valgrind is unable to unwind the stack to
the next function.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390498

--- Comment #2 from r...@sc3d.org ---
I mean, specifically, no callers are listed (no "by" lines).

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390498

r...@sc3d.org changed:

   What|Removed |Added

Summary|Valgrind reports leaks &|Valgrind reports errors
   |other errors in |without full backtrace on
   |vgpreload_memcheck-arm64-li |arm64
   |nux.so  |

--- Comment #1 from r...@sc3d.org ---
I'm sorry, I think I've misunderstood the logs: it's not reporting leaks etc.
in vgpreload_memcheck-arm64-linux.so, it's that I would expect a further
backtrace, but there isn't anything other than the lines I showed above. Still
something odd going on…

-- 
You are receiving this mail because:
You are watching all bug changes.