[Bug 46243] New: wine doesn't work with valgrind' s --progress-interval option

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46243

            Bug ID: 46243
           Summary: wine doesn't work with valgrind's --progress-interval
                    option
           Product: Wine
           Version: 3.21
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, valgrind
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: austinenglish at gmail.com
      Distribution: ---

valgrind-3.14.0 added an option to print its progress. Adding
--progress-interval=1 will print some statistics about its progress every
second.

This works with, for example, yes or bzip2:
austin at laptop:~$ /opt/oldvalgrind/valgrind-3.14.0/bin/valgrind
--progress-interval=1  yes > /dev/null
==11932== Memcheck, a memory error detector
==11932== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==11932== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==11932== Command: yes
==11932== 
--11932-- PROGRESS: U 1s, W 1s, 100.0% CPU, EvC 0.50M, TIn 1.9k, TOut 0.0k,
#thr 1
--11932-- PROGRESS: U 2s, W 2s, 100.0% CPU, EvC 1.20M, TIn 1.9k, TOut 0.0k,
#thr 1
--11932-- PROGRESS: U 3s, W 3s, 100.0% CPU, EvC 1.80M, TIn 1.9k, TOut 0.0k,
#thr 1
--11932-- PROGRESS: U 4s, W 4s, 100.0% CPU, EvC 2.50M, TIn 1.9k, TOut 0.0k,
#thr 1

but when I try that with Wine, nothing:
austin at laptop:~/wine-git$ /opt/oldvalgrind/valgrind-3.14.0/bin/valgrind
--progress-interval=1  ./wine winemine
==12309== Memcheck, a memory error detector
==12309== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==12309== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==12309== Command: ./wine winemine
==12309== 
==12314== 
==12314== HEAP SUMMARY:

This would be incredibly helpful to have working, for knowing when valgrind is
busy versus when it's stuck in a loop.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.