flat assembler
Message board for the users of flat assembler.

Index > Windows > FASMW on Vista 64 - Not Responding

Goto page Previous  1, 2
Author
Thread Post new topic Reply to topic
Suzume



Joined: 07 Oct 2009
Posts: 12
Suzume
Thank you very much, LocoDelAssembly for your engagement and continued support in this matter.

You narrowed it down, it works! Smile

The caret might be missing, but now the IDE is at least usable.
Post 11 Oct 2009, 01:02
View user's profile Send private message Reply with quote
LocoDelAssembly
Your code has a bug


Joined: 06 May 2005
Posts: 4633
Location: Argentina
LocoDelAssembly
Excellent, I'll make the formal bug report then. Very Happy
Post 11 Oct 2009, 01:38
View user's profile Send private message Reply with quote
kohlrak



Joined: 21 Jul 2006
Posts: 1421
Location: Uncle Sam's Pad
kohlrak
What exactly causes the freeze though? If the problem's win64 specific, doesn't this mean it's windows' problem (no reason we can't do something about it until they do fix it though)?
Post 11 Oct 2009, 02:08
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger MSN Messenger Reply with quote
LocoDelAssembly
Your code has a bug


Joined: 06 May 2005
Posts: 4633
Location: Argentina
LocoDelAssembly
I don't know with certainty but the problem may have something to do with this API that doesn't like to have calls to ShowCaret from a WindowProc when WM_OBJECT message is sent. Additionally it seems to be ShowCaret who triggers the WM_OBJECT message and since it is "replied" by calling ShowCaret again then the app gets blocked.
Post 11 Oct 2009, 03:01
View user's profile Send private message Reply with quote
kohlrak



Joined: 21 Jul 2006
Posts: 1421
Location: Uncle Sam's Pad
kohlrak
Take note of the "type" displayed... Is this then something that would be specific to tablet PCs? I'm still not sure i'm getting this (windows is so complex the developers admit they don't even know what's going on when they're making it).
Post 11 Oct 2009, 03:16
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger MSN Messenger Reply with quote
Tomasz Grysztar
Assembly Artist


Joined: 16 Jun 2003
Posts: 7430
Location: Kraków, Poland
Tomasz Grysztar
In fact, this is not the first time that someone reported problem with fasmw on the machine with tablet attached, so perhaps it's related.

I'm sorry I could not respond to this thread earlier, this was a very busy week for me. I have updated the fasmw package for 1.69.08 core with a fix that gets rid of excessive ShowCaret calling. Please test it.
Post 11 Oct 2009, 09:07
View user's profile Send private message Visit poster's website Reply with quote
Suzume



Joined: 07 Oct 2009
Posts: 12
Suzume
I'm going to test the new version right away.
Tablet PC ... something about this drifts at the far horizon of my mind.

"Vista is somehow making a tablet pc out of a notebook as soon as a Wacom graphics tablet is intalled..." I don't know if I recall correctly here.

So that may be relevant - programmers rarely have graphics tablets attached to their notebooks which may be why this behaviour has not been encountered earlier. I do, though I didn't have it connected when I tried to use fasmw.

edit:
Are you sure that you updated the 16908 zip for windows? The fasmw.exe is flagged as being last modfied on 04. Octobre 2009.
The only file from 11th I found at a quick glance was WIN32AX.INC... and compiling the SOURCE into binaries via fasm.exe to a new fasmw.exe didn't show any changes - the IDE still rejects to respond in time.

edit2:
Here's another dump file created from the fasmw.exe that I assembled from the source code which ships with 16908:
http://rapidshare.com/files/291593101/FASMW_dump2.7z.html
MD5: A0093591F50543144A0C4154ED57FFEC
Post 11 Oct 2009, 09:45
View user's profile Send private message Reply with quote
LocoDelAssembly
Your code has a bug


Joined: 06 May 2005
Posts: 4633
Location: Argentina
LocoDelAssembly
Suzume, it is like you said, the new FASMW was not included in the update. I gave a look at your dump anyway. The error is the same but the stack has a difference in the last line:
Code:
000bb6a4 74ba4ee2 000608fc 00000000 000bb6d0 oleacc!LookupWindowClass+0x73    
Original was:
Code:
000bada4 74ba4100 00150740 fffffffc 74ba22a8 oleacc!ORIGINAL_AccessibleObjectFromWindow+0x71    


But perhaps it is not true because I had the message "*** WARNING: symbols timestamp is wrong 0x4791ad89 0x4791a74d for oleacc.dll" in the third line and that may be doing some mess in the interpretation of the symbols.

Just in case I'm missing something I copy it completely:
Code:
0:000:x86> kb
ChildEBP RetAddr  Args to Child              
000bac74 76e5d530 000608fc 0000003d ffffffff user32!NtUserMessageCall+0x15
000bacb0 76e5d568 000608fc 0000003d ffffffff user32!SendMessageTimeoutWorker+0xa6
*** WARNING: symbols timestamp is wrong 0x4791ad89 0x4791a74d for oleacc.dll
000bacd8 74ba41c5 000608fc 0000003d ffffffff user32!SendMessageTimeoutW+0x21
000bad04 74ba4100 000608fc fffffffc 74ba22a8 oleacc!ORIGINAL_AccessibleObjectFromWindow+0x71
000bad28 74bc8bb1 000608fc fffffffc 74ba22a8 oleacc!AccessibleObjectFromWindow+0x1a
000bad64 732f2884 000608fc fffffffc 00000000 oleacc!AccessibleObjectFromEvent+0x5c
000badd8 732feaa9 000608fc fffffffc 00000000 tiptsf!CARET::UpdateMSAAEditFieldState+0x37
000bb050 732f1bad 00000000 000608fc 00008002 tiptsf!CARET::_ProcessCaretEvents+0x82b
000bb080 76e783ec 00010100 00008002 000608fc tiptsf!CARET::ProcessCaretEvents+0x8c
000bb0c0 772ee476 000bb0d8 00000000 000bb42c user32!__ClientCallWinEventProc+0x2e
*** ERROR: Module load completed but symbols could not be loaded for fasmw.exe
000bb0f4 0040b2b3 000608fc 00000000 0040b000 ntdll_772d0000!KiUserCallbackDispatcher+0x2e
WARNING: Stack unwind information not available. Following frames may be wrong.
000bb398 76e58817 000608fc 0000003d 00000000 fasmw+0xb2b3
000bb3c4 76e5898e 0040b000 000608fc 0000003d user32!InternalCallWinProc+0x23
000bb43c 76e59d14 00000000 0040b000 000608fc user32!UserCallWinProcCheckWow+0x109
000bb498 76e59d85 00b9de10 00000000 0000003d user32!DispatchClientMessage+0xe0
000bb4d4 772ee476 000bb4ec 00000000 000bb934 user32!__fnDWORD+0x2b
000bb508 76e5d530 000608fc 0000003d 00000000 ntdll_772d0000!KiUserCallbackDispatcher+0x2e
000bb544 76e5d568 000608fc 0000003d 00000000 user32!SendMessageTimeoutWorker+0xa6
000bb56c 74ba4fa1 000608fc 0000003d 00000000 user32!SendMessageTimeoutW+0x21
000bb6a4 74ba4ee2 000608fc 00000000 000bb6d0 oleacc!LookupWindowClass+0x73    
Post 11 Oct 2009, 17:09
View user's profile Send private message Reply with quote
Tomasz Grysztar
Assembly Artist


Joined: 16 Jun 2003
Posts: 7430
Location: Kraków, Poland
Tomasz Grysztar
Sorry, that was my mistake during the packaging. The correct updated .zip is uploaded now.
Post 11 Oct 2009, 21:07
View user's profile Send private message Visit poster's website Reply with quote
Suzume



Joined: 07 Oct 2009
Posts: 12
Suzume
It works for me now. Thank you! Smile
Post 11 Oct 2009, 22:07
View user's profile Send private message Reply with quote
r22



Joined: 27 Dec 2004
Posts: 805
r22
Quote:
How many ShowCaret's does it take to freeze Vista 64?

Just 1! (with WM recursion) Very Happy
Post 12 Oct 2009, 18:03
View user's profile Send private message AIM Address Yahoo Messenger Reply with quote
Suzume



Joined: 07 Oct 2009
Posts: 12
Suzume
Haha, nice... I'll pin that joke to my desktop background. Wink
Post 12 Oct 2009, 22:16
View user's profile Send private message Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  
Goto page Previous  1, 2

< Last Thread | Next Thread >
Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Copyright © 1999-2019, Tomasz Grysztar.

Powered by rwasa.