[valgrind] [Bug 393146] failing assert "is_DebugInfo_active(di)"

2018-09-03 Thread Michael Kelsey
https://bugs.kde.org/show_bug.cgi?id=393146

--- Comment #15 from Michael Kelsey  ---
Thank you!  The HEAD works for me (MacOSX).

-- 
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

2018-08-15 Thread 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] New: Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g

2018-04-14 Thread Michael Kelsey
https://bugs.kde.org/show_bug.cgi?id=393146

Bug ID: 393146
   Summary: Memcheck fails assert "is_DebugInfo_active(di)" even
though code built with -g
   Product: valgrind
   Version: 3.14 SVN
  Platform: Homebrew (Mac OS X)
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: kel...@slac.stanford.edu
  Target Milestone: ---

Created attachment 112030
  --> https://bugs.kde.org/attachment.cgi?id=112030=edit
Failure report for Memcheck 3.14.0.GIT on High Sierra

I built the HEAD of Valgrind (3.14.0.GIT) via Homebrew, in order to use it on
my recently upgraded MacOSX High Sierra system.  When I run Memcheck with my
application, it crashes out with the attached log file.  The key line is

valgrind: m_debuginfo/debuginfo.c:452 (void
discard_or_archive_DebugInfo(DebugInfo *)): Assertion 'is_DebugInfo_active(di)'
failed.

I can confirm that my application (a Geant4 executable) and its associated
shared libraries are all built with debugging symbols included.

Given the various ongoing problems with High Sierra, I marked this as an
OS-specific issue, probably not a general "bug" in Valgrind.

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