Hi all.
I am working on my IDE and now I am building a Resource Editor for the IDE.
Two days before the Resource Editor worked fine.
Yesterday I added a new function and a new local variable, I rebuild, but my Editor crashed.
I searched the source but I did not find any bug.
After I comment the new source and I restored the source into the previous state but the problem still existed.
I left my PC and I went to sleep.
Today and without making any change I opened my PC and simply I rebuild the program.
It worked fine. After that I added the new source again but the program crashed again
and I received a message from the System that told me that did not find the WINSTA.dll.
I deleted the new source, I rebuild but the problem reappeared.
I restarted my PC and the problem solved.
Does anybody know what happen ?
Thank you,
Manos.
Did you try it with a debugger? You might give us more details.
it may be that "windows file release" issue we discussed in the other thread
but - i don't know what winsta.dll has to do with it
maybe check your machine for viruses ?
QuoteWhat is winsta.dll doing on my computer?
http://www.processlibrary.com/en/directory/files/winsta/25278/
well - i think that library is primarily used for remote desktops, etc
that's what made me think a possible virus (keylogger or something similar)
but, it may be that winsta.dll is the culprit in the file-release issue :redface:
Today I did format of my hard disk.
I reistalled all Tools.
I use VS6.0 and VC++2008 Express.
I had builded my Resource Editor using VC++2008.
I rebuild today my Resource Editor using VC++2008 again, but the problem exists yet.
If I rebuild the Resource Editor and run this, the program crashed.
If I restart my Windows(xp), the program run OK, that is, if I rebuild the program, I must restart Windows.
It is imposible to explain this behavior.
I think that the problem is in VC++2008.
I 'll try to build this with VS6.0 pro.
Manos.
It's a really strange problem ...
Did you try to execute "crash version" of your app under VS debugger?
If not, please try to do it, copy the content of output (DEBUG) window after the program crash and post it here ...
it will increase the possibility that someone here will help you
In WinDbg there's an option to generate the minidump when certain exception occurs ... that's why we need first to look for exception code either in VS debugger or in WinDbg ...
Once we get exception code(s) we can handle it in WinDbg by typing in the command window:
sxe -c ".dump /ma YOUR_DOUBLE_BACKSLASHED_PATH_HERE_\\MINIDUMP_NAME.dmp" EXCEPTION_CODE
As a result we'll get a minidump that can be sent via email (it will not fit attachment's allowed size ) or analyzed locally(the better choice as soon as you have debug symbols for your app and full source code ).
What else comes to my mind is looking to Windows event logs for the records related to your problem ...
...
and instead of rebooting try:
- terminate explorer process and restart it;
- log out and log in again
and see if it helped ( after rebuilding your app)
I used a debugger and I found that I used an uninitialized local variable that was a pointer to a structure.
The problem is solved.
Thank you all.
Manos.