[Kst] [Bug 153654] New: [d2asc] annoying ASSERT messages while running d2asc

[D.V.Wiebe]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=153654         
           Summary: [d2asc] annoying ASSERT messages while running d2asc
           Product: kst
           Version: 1.5.0
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kst kde org
        ReportedBy: dwiebe physics utoronto ca


Version:           1.5.0 (using KDE KDE 3.5.8)
Compiler:          gcc (GCC) 4.1.2 
OS:                Linux

d2asc has the fun side-effect of spamming STDERR with the following:

ASSERT: "myLockStatus() == KstRWLock::WRITELOCKED" in kstrvector.cpp (444)
ASSERT: "myLockStatus() == KstRWLock::WRITELOCKED" in kstrvector.cpp (404)
ASSERT: "myLockStatus() == KstRWLock::WRITELOCKED" in kstrvector.cpp (404)
ASSERT: "myLockStatus() == KstRWLock::WRITELOCKED" in kstrvector.cpp (444)

once per channel output, which can result in reams of them.  It would be swell if they could go away, so I can actually see what I'm doing.