DevLabs > DevLabs Forums > CHESS – Find and Reproduce Concurrency Heisenbugs > concurrencyexplorer - no information available
Ask a questionAsk a question
 

Answerconcurrencyexplorer - no information available

  • Tuesday, July 07, 2009 5:16 PMCorneliu P Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    I would like to see the execution trace using concurrency explorer, but the thread pane display displays "no information available". As far as I can tell, the sourcefile is compiled to produce debugging information:

      cl /LDd /nologo /EHsc /Zi /Oi /MDd /Gm- /W4 /Gs  /D_X86_ /Fefig2.fixed.asplos08.dll /Fdfig2.fixed.asplos08.pdb fig2.fixed.asplos08.cpp  /link  /machine:x86 /debug /debugtype:cv,fixup /release /incremental:no /subsystem:console fig2.fixed.asplos08.cpp
      ..\..\bin\wchess.exe /trace fig2.fixed.asplos08.dll
      ..\..\bin\concurrencyexplorer.exe trace

    Could you please tell me if there is something I'm doing wrong? Btw, how is concurrencyexplorer supposed to know where is the debugging information, the file "trace" created by wchess does not contain any pointer to the c/object input files.

    Thank you for help! (sorry for the naive question :)
     Corneliu

Answers

All Replies

  • Thursday, July 09, 2009 4:41 AMMadan MusuvathiMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi corneliu,
     Can you send your .cpp file to madanm@microsoft.com?
     If thats not possible, can you send me the .dll, .pdb, and the trace file.

    thanks
    madan
  • Wednesday, August 05, 2009 7:36 PMDavid Harwin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    What version of Windows are you using? I had the same issue when using the sample code provided. I watched ProcMon while running "wchess /trace test.dll" and noticed that it opened the pdb file (so it wasn't a configuration issue of being unable to locate the source) but the trace file did not include any references to cpp files. After running the same steps on various systems, I noticed that this reproduced on XP64 and Server 2003, but when I moved to a Vista or Windows 7 system (either 32- or 64-bit), the trace file included the correct source code references and concurrencyexplorer.exe displayed useful output. It could be an issue in the Win2k3 wrapper library.

    Each machine had the same software configuration:
    CHESS 0.1.30626.0
    Visual Studio 2008 Team System with SP1
    Windows SDK 6.0.6001.18000.367

    I hope this helps.
            David