A couple of days ago I mentioned that I was having some problems with loading symbols for a common controls dll. I'm now pretty sure that it was my problem, as usual, rather than someone elses. I've reworked my process startup controlling code and now set and clear the breakpoints in a more reliable (i.e. less hacky) way and things are behaving themselves again. I think I was failing to stop one of the threads properly and that was later causing problems.
I think the weirdness was me
Categories:
Follow me on Twitter: @LenHolgate
About this Entry
DbgHelp weirdness was the previous entry in this blog.
Naming Win32 threads - how it works is the next entry in this blog.
I usually write about C++ development on Windows platforms, but I often ramble on about other less technical stuff...
Find recent content on the main index or look in the archives to find all content.
Recent Entries
- C++ Tools - Deleaker
- C++ Tools - CppDepend - 2017 update...
- VMWare bridged networking intermittently failing
- How to determine if a non-IFS LSP is installed
- C++ Tools - JetBrains ReSharper C++ - purchased...
- C++ Tools - CppDepend
- Practical Testing: 37 - Bringing the code up to date
- C++ Tools - JetBrains ReSharper C++ is slowly winning me over
- Practical Testing: 36 - Timeout handle wrap
- Practical Testing: 35 - Heap corruption
I have other blogs...
The Server Framework - high performance server development
Lock Explorer - deadlock detection and multi-threaded performance tools
l'Hexapod - embedded electronics and robotics
MegèveSki - skiing
I also write about...
.Net
Books
C++ Tips
CC.Net
CLR Hosting
CORBA
Continuous Integration
Debugging Tools
Dumbing down is dumb
ENet
Geek Speak
General
Get a life
Holiday Pictures
Java
Linux
Lock Explorer
Managed XLL
OLEDB
Rants
Refactoring
Reprints
Role Playing
Socket Servers
Sound and Vision
Source Code
Testing
Way back
Winsock Registered I/O
x64
Leave a comment