Create regular radasm project and paste this code



include header.inc

.code
start:

PrintHex eax
invoke Sleep,10000

invoke ExitProcess,0
end start




output window will not show value in eax right after PrintHex is executed, instead it will wait program end (10 seconds) also whole radasm will be blocked during that... is there any solution for this?
All this applies for RadASM 2.0.1.8 (04/23/2003 release) and vkdebug that comes withing masm v8 package
for RadASM 1.2 there was not this problem

(also where can i get latests and bugfixed vkdebug?)
thanks
Posted on 2003-04-25 19:06:25 by Mikky
I tried to copy and paste your code (with my own header just included the normal stuff) and could not re-create the problem. I used the VKim v1.1 from the MASM32 V8 folder and the debug window appeared instantly.

My test Prog:
;##########################

; Compiler directives

.486
.model flat, stdcall
option casemap:none

;##########################
; Include files

include \masm32\include\windows.inc

include \masm32\include\shell32.inc
include \masm32\include\user32.inc
include \masm32\include\kernel32.inc
include \masm32\include\masm32.inc

;##########################
; Libraries

includelib \masm32\lib\shell32.lib
includelib \masm32\lib\user32.lib
includelib \masm32\lib\kernel32.lib
includelib \masm32\lib\masm32.lib

;##########################
; VKim's Debug

include \masm32\include\debug.inc
includelib \masm32\lib\debug.lib

DBGWIN_DEBUG_ON = 1 ; include debug info into the program
DBGWIN_EXT_INFO = 0 ; include extra debug info into the program

;##########################
.code
start:

PrintHex eax
invoke Sleep,10000

invoke ExitProcess,0
end start
Posted on 2003-04-25 23:33:23 by donkey
ok I was thinking on output window within RADAsm, not vkdebug output windiw which is separate app
thats how Ive been debuging in RadASm 1.2 version and wanted to continue with new 2.0
I will check your code now
Posted on 2003-04-26 04:31:46 by Mikky
ok Ive just found out that vkdebug I was using is the one that comes with radasm package
its in
\radasm\masm\inc\debug.inc
\radasm\masm\lib\debug.lib

so I ve changed header and included those debug files from masm v8 but now there is another problem,

LINK : fatal error LNK1104: cannot open file "\masm32\lib\kernel32.lib"

this is some error in debug.lib, since if I exclude that file from header program assembles with no errors

basically all I want is to use vkdebug with radasm2.0 output window and thats all
Posted on 2003-04-26 05:35:19 by Mikky
That's something up with your program or your lib files, again it compiles fine here. You must include the following minimum dependancies in your program to use Vkim's debugger:

include \masm32\include\windows.inc
include \masm32\include\kernel32.inc
include \masm32\include\masm32.inc
includelib \masm32\lib\kernel32.lib
includelib \masm32\lib\masm32.lib

EDIT : The only known bug in VKim's debug can be found here
Posted on 2003-04-26 09:32:46 by donkey
ok can you confirm me if vkdebug works fine with radasm's output window (I am not talking about dbgwin.exe that is part of vkdebug package)
if thats true then its definately somthing wrong at me
Posted on 2003-04-26 13:53:21 by Mikky
There is definitely the issue that you have described it in your first post. I never use the integrated debug so I have never noticed it before. It appears that your routine does not give RadASM a chance to update the output window, the debugger is working properly but because you fall into an effective tight loop directly after the command RadASM does not have the time to display the number until the loop is finished.
Posted on 2003-04-26 14:19:02 by donkey
yes, and this was not the problem with previous radasm version 1.2
well I guess I will have to discard old habit and use vk debug window from now on

btw anyone else wanna join party in this thread... ketil0? :)
Posted on 2003-04-26 20:19:25 by Mikky