FiveTech Software tech support forums

Antonio,

I am able to get the before vminit in the maindll.c not the one before in the hvm.c

Thanks

... clean install > make_gnu.log 2>&1copy \hs1\harbour\bin\*.exe \harbour\bin\  Here is what I have in the hvm.c file. /* application entry point */#include <windows.h>  // new !!!void hb_vmInit( BOOL bStartMainProc ){   HB_TRACE(HB_TR_DEBUG, ...

Antonio, Yes, I forgot the #include <windows.h> inside hvm.c I put it in there and still having some sort of problems. When I added the messages in the HVM I was still not hitting them To be sure I started over fresh with no changes I noticed this ...

Dave, > Error: Unresolved external '_MessageBox' referenced from C:\HS\HARBOUR\LIB\WIN\BCC\HBVM.LIB|hvm Do you get that error when building your DLL ? Or when you rebuild Harbour ? Have you included #include <windows.h> inside hvm.c as I shown you ? > also this ...

Antonio, I keep getting compile error Error: Unresolved external '_MessageBox' referenced from C:\HS\HARBOUR\LIB\WIN\BCC\HBVM.LIB|hvm also this is how the initstack is. #if defined( HB_MT_VM )   hb_threadInit();   hb_vmStackInit( hb_threadStateNew() ...

Dave, Ok, now in Harbour\source\vm\hvm.c function hb_vmInit() please place some traces and rebuild Harbour again and rebuild the DLL and the EXE: ...#include <windows.h>  // new !!! void hb_vmInit( BOOL bStartMainProc ){  ...

... source\vm\extend.c: source\vm\extrap.c: source\vm\fm.c: source\vm\garbage.c: source\vm\hashes.c: source\vm\hashfunc.c: source\vm\hvm.c: source\vm\initexit.c: source\vm\initsymb.c: source\vm\itemapi.c: source\vm\macro.c: source\vm\memvars.c: source\vm\memvclip.c: source\vm\pcount.c: ...

... source\vm\extend.c: source\vm\extrap.c: source\vm\fm.c: source\vm\garbage.c: source\vm\hashes.c: source\vm\hashfunc.c: source\vm\hvm.c: source\vm\initexit.c: source\vm\initsymb.c: source\vm\itemapi.c: source\vm\macro.c: source\vm\memvars.c: source\vm\memvclip.c: source\vm\pcount.c: ...

Dave,

Do you have experience building Harbour yourself ?

We should place several traces in harbour\source\vm\hvm.c function hb_vmInit() to check where it is failing.

Its easy. I can explain you how to do it.

... Microsoft (R) C/C++ Optimizing Compiler Version 12.20.9615 for ARM Copyright (C) Microsoft Corp 1984-2002. All rights reserved. tosfrit.c hbvm.lib(hvm.obj) : warning LNK1166: cannot adjust code at offset=0x00001000, rva=0x000580BC hbmacro.lib(macrob.obj) : warning LNK1166: cannot adjust code at ...

... external '_hb_errInternal' referenced from C:\HARBOUR\LIB\VM.LIB|fm Error: Unresolved external '_hb_errInit' referenced from C:\HARBOUR\LIB\VM.LIB|hvm Error: Unresolved external '_hb_conNewLine' referenced from C:\HARBOUR\LIB\VM.LIB|estack Error: Unresolved external '_hb_conOutErr' referenced from ...

... 22:30 UTC-0430 Ron Pinkas <ron/at/xharbour.com> * include/classes.h * source/vm/classes.c + Added hb_clsClearAllClassDatas() * source/vm/hvm.c + Add call to clear class datas before disabling Destructors /* This change dismisses the restriction on storing a destructable object into a ...

No, as far as I know. This is from xHarbour's hvm.c: #ifdef TRACE_DUPLICATE_FUNCTIONS /* NOTE: hb_traceInit() is not yet executed, but it uses s_bEmpty to not override output preceding hb_vmInit() */ TraceLog( NULL, "*** ...

... for ARM Copyright <C> Microsoft Corp 1984-2002. All rights reserved. Client.c Creating library client.lib and object client.exp Vm.lib(hvm.obj) : warning LNK1166: cannot adjust code at offset=0x00001000, rva= 0x00038328 rdd.lib(dbf1.obj) : warning LNK1166: cannot adjust code at offset=0x00001000, ...

Unfortunately not. This log comes from xHarbour not from FWH and is not currently optional. While waiting for the new xHarbour official release, you can comment out the line with the string "WARNING!" from hvm.c of the CVS (or I can send you harbour.exe with that change).

EMG