Issue-#108 BlackBox Start up warnings

[Ivan Denisov]

I mean that the bug is old. There is this bug in 1.6 final. So I would you to try 1.5. Is there error message if you start 1.5 with incompatible Converters in working directory?

[Josef Templ]

I have tested it now under XP and it still shows the expected error message.
Please look carefully if there is a dialog box being opened. May be you are overlooking such a dialog box.
Is it possible that there is some non-standard tool involved, like midnight commander or any other shell
that causes the behavior?

For anybody who can reproduce the problem it should be easy to debug it.
Just insert HALT statements and see how far it proceeds.
Start in Kernel.Init, then look into Kernel.InitModule, then into the individual modules being initialized.

- Josef

[DGDanforth]

I have tested it now under XP and it still shows the expected error message.
Please look carefully if there is a dialog box being opened. May be you are overlooking such a dialog box.
Is it possible that there is some non-standard tool involved, like midnight commander or any other shell
that causes the behavior?

For anybody who can reproduce the problem it should be easy to debug it.
Just insert HALT statements and see how far it proceeds.
Start in Kernel.Init, then look into Kernel.InitModule, then into the individual modules being initialized.

- Josef

Josef,
(1a) HALT inserted into body of Kernel.odc, StdLoader.odc, Init.odc and compiled with master.
(1b) master run via shortcut with /USE
(1c) nothing happens. Nothing halts.
(1d) remove Converters then the master traps

But now we are in a predicament. The thing we are trying to locate blocks its location.
I even tried creating Startup.Setup with a HALT but that does not trap when Converters is present.

-Doug

[DGDanforth]

I have tested it now under XP and it still shows the expected error message.
Please look carefully if there is a dialog box being opened.

No dialog box anywhere.

[DGDanforth]

Another problem with using HALT is that the Kernel is linked.
The behavior I see is that the Kernel does not trap.
Only modules, such as, Init will tap with a HALT.

But it seems that Converters aborts the load process before Init is called.

-Doug

[Josef Templ]

You need to relink a new .exe file if you modify any of the 4 linked modules.
See Dev/Docu/Build-Tool, for how to do it.

It is in principle possible that there is an uninitialized variable involved somewhere in the error reporting code
leading to the observed non-deterministic behavior.
Putting in a HALT will probably not change this as it does not write to any local variables.

- Josef

[DGDanforth]

You need to relink a new .exe file if you modify any of the 4 linked modules.
See Dev/Docu/Build-Tool, for how to do it.

It is in principle possible that there is an uninitialized variable involved somewhere in the error reporting code
leading to the observed non-deterministic behavior.
Putting in a HALT will probably not change this as it does not write to any local variables.

- Josef

SNAFU!

I have MyBuilder which creates .exe files.
I copied Kernel to KernelTest and inserted HALT.
I linked that into BBTest.
The Kernel did trap. Good.
I then realized I had not used the BB1.6 Converters so attempted to do that BUT
DevLinker complained (as it should)

Meta.Item imported from Converters has wrong fprint
Files.File^ imported from Converters has wrong fprint

Hence I can not build an .exe file to exhibit the behavior we wish to track.
-Doug

[DGDanforth]

More strange behavior.
If I place HALT(99) into master Converters.odc at BEGIN and compile it then master.exe does nothing.
If I comment out the HALT and recompile then the master starts normally.
-Doug

[DGDanforth]

I believe the previous behavior is the simplest to test. It is master using master.

Will everyone please do in the master

Code: Select all

BEGIN
	HALT(99);
	list := NIL
END Converters.

compile (keep open the master so you can undo the change) and then execute BlackBox.exe

Please tell me what you see.

-Doug

[Ivan Denisov]

In windows 7 there is no problem. Trap message showing well.

trap.png (29.1 KiB) Viewed 12230 times