FiveTech Software tech support forums

Posted: **Thu Sep 26, 2024 5:18 pm**

Never mind, there was a problem in the xHarbour/MSC32 build. Now it is fixed:

http://www.xharbour.org/files/download/ ... vc2022.zip

Posted: **Thu Sep 26, 2024 9:37 pm**

As a resume:

TEST HB_GCALL()

MSC32: OK
MSC64: CRASH
BCC32: OK
BCC64: CRASH

Posted: **Fri Sep 27, 2024 10:25 am**

What is this method for?

fwmariarowset_Destroy()

If I remove it the crash goes away. And also if I replace DESTRUCTOR with METHOD.

Posted: **Fri Sep 27, 2024 11:04 am**

In fwmariarowset_Destroy(), if I put

? k

the result is

4171717171

Something wrong here...

Posted: **Mon Sep 30, 2024 11:53 am**

Can we restrict the destructor method not to work with xHarbour 64 bits only?
Let me try

Posted: **Mon Sep 30, 2024 12:24 pm**

Yes, we can.

Posted: **Mon Sep 30, 2024 12:42 pm**

At the top of the module

#ifdef __XHARBOUR__
#ifdef __64__
#define __XHARBOUR64__
#endif
#endif

#ifndef __XHARBOUR64__
   DESTRUCTOR fwmariarowset_Destroy()
#endif

Next apply the same condition to the entire body of the Procedure

Do you think this should be ok?

Posted: **Mon Sep 30, 2024 1:05 pm**

Yes, I think so. But the question is: why do you need an explicit destructor?

Bug Maria_Connect() FWH-24.07 64 bits ???