Bug 153654

Summary: [d2asc] annoying ASSERT messages while running d2asc
Product: [Applications] kst Reporter: D. V. Wiebe <dvw>
Component: generalAssignee: kst
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 1.5.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description D. V. Wiebe 2007-12-07 23:33:33 UTC 
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.
Comment 1 D. V. Wiebe 2007-12-08 00:42:09 UTC 
> The appropriate configure options fix this (disable debug or some such...)


Hmmm... AFAICT my kst package was built with:

  ./configure --disable-debug

I'll rebuild it tonight with that switch (so I can be sure) and see if the
problem persists.

-dvw
Comment 2 D. V. Wiebe 2007-12-08 01:29:50 UTC 
I just rebuilt d2asc with --disable-debug and the ASSERTs are still there.
Comment 3 Andrew Walker 2007-12-11 01:39:50 UTC 
The assert should either be avoided (if it is a valid assert) or the assert should be removed (if it is an invalid assert).
Comment 4 Andrew Walker 2007-12-11 01:53:37 UTC 
SVN commit 747086 by arwalker:

BUG:153654 add necessary locks to avoid asserts

 M  +9 -5      d2asc.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=747086