The instruction at "0x0044ab7b referenced memory at....

[Taavi]

Hello,
after every runtime error in our applications we get additional error message saying:
"The instruction at "0x0044ab7b" referenced memory at "0x00000000".
The memory could not be "read".

I was able to recreate error with Fivewin testmdi6 (slightly modified, code attached) sample. Just press button on buttonbar and You will get normal runtime error and this memory error after this.

Comment out creating 2-nd child and no memory read error after runtime
error message....

Using xHarbour (Jan 2007) and FWH 200612 builds, the same was with FWH 200609.

Any ideas?

Taavi.


////Test Code start

// Controlling MDI menus - Dynamically changing MDIChild windows menus

#include "FiveWin.ch"

static oWnd

//----------------------------------------------------------------------------//

function Main()
local oChild1, oChild2, oChild3
local oBar,x:=''

DEFINE WINDOW oWnd TITLE "Controlling MDI menus" MDI

DEFINE WINDOW oChild1 MDICHILD TITLE "First Child"
ACTIVATE WINDOW oChild1

//Comment out next 2 lines and no second errormessage after runtime error...
DEFINE WINDOW oChild2 MDICHILD TITLE "Second Child" // No Menu for this
ACTIVATE WINDOW oChild2


DEFINE BUTTONBAR oBar OF oWnd
DEFINE BUTTON OF oBar ACTION (x+1) //To generate runtime error...

ACTIVATE WINDOW oWnd

return nil

[James Bott]

Taavi,

I confirm the error with FWH Aug 2006 build and xHarbour.

I thought that maybe it was because the child windows weren't declared with the OF oWnd clause, but adding that didn't solve the problem.

James

[Enrico Maria Giordano]

Code: Select all

local oBar,x:=0//''

EMG

[Taavi]

Code: Select all

local oBar,x:=0//''

EMG

Hi,
this was intentional, to generate runtime error...

Can You also see second screen with memory error?

Taavi.