[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Moritz Bunkus]

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

Moritz Bunkus  changed:

   What|Removed |Added

 CC||mor...@bunkus.org

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Michał Walenciak]

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

Michał Walenciak  changed:

   What|Removed |Added

 CC||kice...@gmail.com

--- Comment #11 from Michał Walenciak  ---
I can confirm William's words - any Qt app on Arch Linux causes this error.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[William Findlay]

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

William Findlay  changed:

   What|Removed |Added

 CC||will...@wfindlay.com

--- Comment #10 from William Findlay  ---
(In reply to Johannes Jordan from comment #9)
I can confirm I have the same problem with all my Qt5 apps with the most recent
version of valgrind. On Arch Linux 4.18.5.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Martin Apel]

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

Martin Apel  changed:

   What|Removed |Added

 CC||martin.a...@3ds.com

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Johannes Jordan]

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

--- Comment #9 from Johannes Jordan  ---
Created attachment 114650
  --> https://bugs.kde.org/attachment.cgi?id=114650=edit
Minimal example that uses Qt QApplication

This is a minimal example that triggers the problem on my GNU/Linux system. It
is a barebone Qt application. I have Qt 5.11.1 installed on my system. You can
either try to use the Makefile directly or run 'qmake minimal-example.pro' to
generate one that fits your system.

Note that running valgrind on *any* Qt5 application binary on my system
triggers this problem. Which is expected given the nature of this minimal
example.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Philippe Waroquiers]

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

--- Comment #8 from Philippe Waroquiers  ---
(In reply to Johannes Jordan from comment #7)
> Anything I can do to help fix this problem?

I think a small compilable reproducer would help.
(I however cannot help much, I do not have a MACOS system)

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Johannes Jordan]

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

Johannes Jordan  changed:

   What|Removed |Added

 CC||k...@lanrules.de

--- Comment #7 from Johannes Jordan  ---
I also ran into this problem today. I have a GNU/Linux system as well. It
doesn't matter if I try the Release or Debug build of my software. For Debug
build I use:
g++ version 8.2.0 with options -fopenmp -g -std=gnu++1z

I tried Valgrind 3.13.0+290+2b0aa0a5-1 as well as git at fee5954ae which seems
to include both the commit you mentioned as well as the patch (c263702101,
b3fc500a9f). The result is the same.

Anything I can do to help fix this problem?

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Michael Kelsey]

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

--- Comment #6 from Michael Kelsey  ---
Thank you!  I tried the Git trunk (via Homebrew), but I see the same behaviour
as before.  I note that in the diff you attached, the line

  vg_assert(is_DebugInfo_active(di));

is still there.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Julian Seward]

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

--- Comment #5 from Julian Seward  ---
Created attachment 114438
  --> https://bugs.kde.org/attachment.cgi?id=114438=edit
valgrind-bug393146-possible-fixes.diff

> Running into the same issue on two different macs (one installed via 
> compiling > the source, one via brew):

I've been working to fix a number of debuginfo reading problems lately,
although on Linux, not OS/X.  Try the git trunk, which contains
one important fix (e752326cc050803c3bcfde1f8606bead66ff9642) with the
attached patch, which contains as-yet uncommitted fixes, on top of it.

I don't know if the combination will fix the OS/X debuginfo reading
problems, but they do help on Linux.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Mike]

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

Mike  changed:

   What|Removed |Added

 CC||cmsim...@gmail.com

--- Comment #4 from Mike  ---
Running into the same issue on two different macs (one installed via compiling
the source, one via brew):

https://pastebin.com/BdifEEQ4

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Philippe Waroquiers]

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

--- Comment #3 from Philippe Waroquiers  ---
(In reply to Julian Seward from comment #2)
> I just hit this on x86_64 Linux, so maybe it's not OSX specific.
Groinch :(.
I guess you have no systematic reproducer ?

Do you still have the host stacktrace ?
The attachment from OSX contains no readable host stack trace.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 CC||jsew...@acm.org,
   ||philippe.waroquiers@skynet.
   ||be

--- Comment #2 from Julian Seward  ---
I just hit this on x86_64 Linux, so maybe it's not OSX specific.

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Ellis Breen]

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

Ellis Breen  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Ellis Breen]

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

Ellis Breen  changed:

   What|Removed |Added

 CC||ellis.br...@gmail.com

--- Comment #1 from Ellis Breen  ---
Have seen the same. A quick workaround seems to shortcut is_DebugInfo_active:

>From be6aba76267a1302fb72db8836e83023e4971203 Mon Sep 17 00:00:00 2001
From: Ellis Breen 
Date: Tue, 26 Jun 2018 17:32:54 +0100
Subject: [PATCH] 393146: Temporary workaround for Darwin

---
 coregrind/m_debuginfo/debuginfo.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/coregrind/m_debuginfo/debuginfo.c
b/coregrind/m_debuginfo/debuginfo.c
index 13991b69a..ab05330b4 100644
--- a/coregrind/m_debuginfo/debuginfo.c
+++ b/coregrind/m_debuginfo/debuginfo.c
@@ -162,6 +162,8 @@ static inline Bool is_DebugInfo_allocated ( const
DebugInfo* di )
 // Is this DebugInfo currently "active" (valid for the current epoch) ?
 static inline Bool is_DebugInfo_active ( const DebugInfo* di )
 {
+// Temporary workaround for 393146
+#ifndef VGO_darwin
if (!is_DiEpoch_INVALID(di->first_epoch)
&& is_DiEpoch_INVALID(di->last_epoch)) {
   // Yes it is active.  Sanity check ..
@@ -170,6 +172,9 @@ static inline Bool is_DebugInfo_active ( const DebugInfo*
di )
} else {
   return False;
}
+#else
+   return True;
+#endif
 }

 // Is this DebugInfo currently "archived" ?
-- 
2.17.1

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[bugzilla_noreply]

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

spartac...@gmail.com changed:

   What|Removed |Added

 CC||spartac...@gmail.com

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

[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

[Rhys Kidd]

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

Rhys Kidd  changed:

   What|Removed |Added

   Assignee|jsew...@acm.org |rhysk...@gmail.com
 CC||rhysk...@gmail.com

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