hmmm, can't quite tell how facetious you are being, or more importantly who you are ;-)
the hope for the ollydbg forums is not to mirror the general (and very good) forums such as http://ollydbg.win32asmcommunity.net/ but rather to serve as a place to discuss more advanced usage and plug-in development.
the whole site is an experiment so the forums could very well be changing. what you see is the first list of topics i put together and thought would be pertinent.
facetious you mean in the sense of joke or may be jocular
nope i am not joking you do have an impressive list of
famous users registered to your forum :)
or more importantly
i dont know if you remember the guy who writes exotic codes :)
any way hope this place will develop into a good place for discussing some finer nuances of ollydbg :)
thanks and regards
as always some anonymouse nicks
hi pedram ,
give away identity :) is the identity that will be given away an identity in the first place :) any way else it turns into offtopic let me get into the matter
i was searching why for that deadlock hang crap on
and in the process i happened to read this blog from
mgrier looks like he hits the point
[quote]
Calling any function from within your DLL_PROCESS_ATTACH which requires synchronization can deadlock.
Obviously it doesn't have to deadlock; a lot of folks get away with a lot of bad stuff. They're getting lucky for the most part.
A great example is the process heap. Did you know that you can lock it? You can! You can probably have a lot of fun by calling HeapLock(GetProcessHeap())? Why would you do that? I don't know! Who can know? Can we stop it? People want to but just wait for the black helicopter crowd to show up saying that it's really a collusion/conspiracy to get people to upgrade software on Windows.
If someone locks it (or maybe calls HeapWalk on the process heap which I assume locks it for the duration of the walk) and then calls into the loader... well... boom. You're deadlocked.
Those are two easy cases. Clearly you can deadlock in additional ways (RPC calls to another process or machine which have to reenter your process on a different thread which then might need the Mythical Loader Lock) and being creative with things like the thread pool, windows messages, etc. you can come up with a million variations on the theme.
Thus, DLL_PROCESS_ATTACH rule #1:
Don't do anything that requires synchronization. Currently, even heap allocation is suspect.
[/quote]
the link
http://blogs.msdn.com/mgrier/archive/2005/06/21/431378.aspx
hope you get some research material :)
Note: Registration is required to post to the forums.