[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 Tom Hughes changed: What|Removed |Added CC||kuo...@gmail.com --- Comment #9 from Tom Hughes -

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 Tom Hughes changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail becau

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #6 from Aaron Merey --- (In reply to Tom Hughes from comment #4) > No that patch won't help. > > The debugname variable is just the name of the file to look for and is in > fact pretty much always set. > > If .gnu_debuglink was present the

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #5 from Tom Hughes --- Created attachment 138358 --> https://bugs.kde.org/attachment.cgi?id=138358&action=edit Patch to avoid looking for a debuginfo image if the main image has debugging This patch does work for me by avoiding looking fo

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #4 from Tom Hughes --- No that patch won't help. The debugname variable is just the name of the file to look for and is in fact pretty much always set. If .gnu_debuglink was present then crc would be set but modern systems don't use that a

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #3 from Aaron Merey --- Created attachment 138194 --> https://bugs.kde.org/attachment.cgi?id=138194&action=edit patch It looks like these unnecessary queries occur when no .gnu_debuglink section is present in a binary but valgrind neverth

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #2 from Tom Hughes --- Just to be clear, the libraries I'm talking about here have debug information (that is to say that have populated .debug_xxx sections) but they do not have separate debuginfo images. -- You are receiving this mail be

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 Mark Wielaard changed: What|Removed |Added CC||f...@redhat.com, |

[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information

https://bugs.kde.org/show_bug.cgi?id=435908 Tom Hughes changed: What|Removed |Added CC||ame...@redhat.com -- You are receiving this mail