From kde-bugs-dist  Tue Mar 01 22:28:33 2011
From: Harri Porten <porten () kde ! org>
Date: Tue, 01 Mar 2011 22:28:33 +0000
To: kde-bugs-dist
Subject: [Bug 267413] New: Assertion 'DRD_(g_threadinfo)[tid].synchr_nesting
Message-Id: <bug-267413-17878 () http ! bugs ! kde ! org/>
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=129901840506561

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

           Summary: Assertion 'DRD_(g_threadinfo)[tid].synchr_nesting >=
                    1' failed.
           Product: valgrind
           Version: 3.7 SVN
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: drd
        AssignedTo: bart.vanassche@gmail.com
        ReportedBy: porten@kde.org


Checking an application with the DRD tool I get the assertion error mentioned
in the summary. Quite possibly that the application is buggy. I have seen mutex
errors on shutdown which is when the tool errors out as well.

I can prepare a source package to reproduce the problem if desired.

$ /opt/valgrind/bin/valgrind --tool=drd ./build -j5
==17339== drd, a thread error detector
==17339== Copyright (C) 2006-2010, and GNU GPL'd, by Bart Van Assche.
==17339== Using Valgrind-3.7.0.SVN and LibVEX; rerun with -h for copyright info
==17339== Command: ./build -j5
==17339== 
Build successful.


drd: drd_thread.c:688 (vgDrd_thread_leave_synchr): Assertion
'DRD_(g_threadinfo)[tid].synchr_nesting >= 1' failed.
==17339==    at 0x38019317: report_and_quit (m_libcassert.c:193)
==17339==    by 0x38019550: vgPlain_assert_fail (m_libcassert.c:267)
==17339==    by 0x3800493F: vgDrd_thread_leave_synchr (drd_thread.c:688)
==17339==    by 0x38001E4D: handle_client_request (drd_clientreq.c:342)
==17339==    by 0x38054A2E: vgPlain_scheduler (scheduler.c:1600)
==17339==    by 0x3807DF84: run_a_thread_NORETURN (syswrap-linux.c:94)
==17339==    by 0x3807E1AA: vgModuleLocal_start_thread_NORETURN
(syswrap-linux.c:225)
==17339==    by 0x38080B4D: ??? (in /opt/valgrind/lib/valgrind/drd-amd64-linux)
==17339==    by 0xDEADBEEFDEADBEEE: ???
==17339==    by 0xDEADBEEFDEADBEEE: ???
==17339==    by 0xDEADBEEFDEADBEEE: ???

sched status:
  running_tid=2

Thread 1: status = VgTs_WaitSys
==17339==    at 0x4E3EBE5: pthread_join (pthread_join.c:89)
==17339==    by 0x4C2FBF4: pthread_join (drd_pthread_intercepts.c:459)
==17339==    by 0x416A90: Thread::waitForDeath() (thread_unix.cpp:79)
==17339==    by 0x41103A: build(Interpreter*, BuildConfig const&)
(ext_build.cpp:807)
==17339==    by 0x42B23F: main (build.cpp:138)

Thread 2: status = VgTs_Runnable
==17339==    at 0x4C31591: pthread_cond_wait@* (drd_pthread_intercepts.c:701)
==17339==    by 0x41670E: WaitCondition::wait(Mutex*) (thread_unix.cpp:139)
==17339==    by 0x40D2C4: processJobs(ThreadInfo*, std::string*)
(ext_build.cpp:743)
==17339==    by 0x40D55D: startThread(void*) (ext_build.cpp:770)
==17339==    by 0x416809: startFuncHelper (thread_unix.cpp:42)
==17339==    by 0x4C30A20: vgDrd_thread_wrapper (drd_pthread_intercepts.c:281)
==17339==    by 0x4E3D8B9: start_thread (pthread_create.c:300)
==17339==    by 0x58CE02C: clone (clone.S:112)

Thread 4: status = VgTs_WaitSys
==17339==    at 0x4E44D65: __lll_unlock_wake (lowlevellock.S:366)
==17339==    by 0x4E41543: _L_unlock_548 (pthread_mutex_unlock.c:290)
==17339==    by 0x4E41472: __pthread_mutex_unlock_usercnt
(pthread_mutex_unlock.c:52)
==17339==    by 0x4C31C32: pthread_mutex_unlock (drd_pthread_intercepts.c:643)
==17339==    by 0x4168CB: Mutex::unlock() (thread_unix.cpp:113)
==17339==    by 0x40D461: processJobs(ThreadInfo*, std::string*)
(ext_build.cpp:758)
==17339==    by 0x40D55D: startThread(void*) (ext_build.cpp:770)
==17339==    by 0x416809: startFuncHelper (thread_unix.cpp:42)
==17339==    by 0x4C30A20: vgDrd_thread_wrapper (drd_pthread_intercepts.c:281)
==17339==    by 0x4E3D8B9: start_thread (pthread_create.c:300)
==17339==    by 0x58CE02C: clone (clone.S:112)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.