RE: Multi thread appli

Hi Salam,

Thanks for your post.

The question you asked is a big topic. Anyway, I will provide some general
information and resource for your reference.

Multithreading application is difficult to debug, and it may cause many
potential problems. The most difficult part of multithread debugging is
that the bug may lies with time and can not be always reproduced out.

The below article talks how to debug multithread application from developer
perspective:
"A Lesson in Multithreaded Bugs"
http://www.windevnet.com/documents/s=7301/wdj9804b/9804b.htm

The article below introduces a deadlock detection library:
http://www.microsoft.com/msj/1098/bugslayer/bugslayer1098.aspx

Personally, I highly recommanded 2 books:
"Debugging Windows Programs: Strategies, Tools, and Techniques for Visual
C++ Programmers"
http://www.zabada.com/zabada/amazon/viewItem?id=020170238X
"Debugging Applications for Microsoft® .NET and Microsoft Windows® "
http://www.microsoft.com/mspress/books/toc/5822.asp

Both of these 2 books have a dedicated chapter regarding multithread
debugging.

Hope this information helps

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

.

Relevant Pages

  • Re: Wieder Probleme mit Linker
    ... >> statische Multithread debug lib ohne MFC. ... > Ich bin mir nicht 100% sicherl, aber verschiedene Runtimes schreien ...
    (microsoft.public.de.vc)
  • Wieder Probleme mit Linker
    ... statische Multithread debug lib ohne MFC. ... Wenn ich nun die LIB die die DLL kommen folgende Fehlermeldungen: ...
    (microsoft.public.de.vc)
  • How to debug "new operator" crash ?
    ... My program is a multithread application, ... to debug this case? ... Here is the call stacks: ... 08!new classB object ...
    (microsoft.public.vc.language)
  • Re: Advanced c++ debugging techniques on Unix
    ... books, tools or libs on advanced c++ debugging techniques on Unix. ... Segmentation faults are relatively easy to debug, logical faults require lots of printf/cout. ... But mostly debugging depends on program design - I write my programs so that errors will lead to an immediate chrash and get my program so safe that this doesn't occur;-) Also using several small modules instead of few large ones helps if you can identify by the nature of the error which module is concerned... ...
    (comp.os.linux.development.apps)