I used C:\FB\FreeBASIC-1.08.1-winlibs-gcc-9.3.0\fbc -g -s gui -gen GAS64 "DSS.bas"
And then tried your new version of the debugger v3beta.
The output window contains lots of
Proc =
End of proc
Followed by
Loading 0
...
Loading 197
Then lots of
debug-event ... Stopcode = 0
statements Intermixed with lots of
Debug Event Exception adr= 140736...
--------------------------------------------
Exception Breakpoint 140736...
Finally, a window appears with title debug string
onecore\com\combase\dcomrem\resolver.cxx(2299)\combase.dll!00007fffd0eb206d: (called: 00007FFFD0EB4F4e) ReturnHR(1)tid(2d64) 80070422
The service cannot be started either because it is disabled or because it has no enabled devices associated with it.
I hit OK and similar messages keep coming with different addresses.
My program which starts with
Code: Select all
Screen 21
Print "Start"
Sleep 5000
The Proc/Var window seems to indicate that nothing is initialized yet (everything is zero).
The left screen displays the file containing the Constructor/Destructor/other routines for a "TYPE Chain" UDT and highlights the first line of a constructor. I suspect that this is the first Constructor executed. I moved a few lines around and each time it highlights the first line of a different constructor.
I am not sure how to proceed from here. I will continue to study the initial startup code to see if I can find anything. But cannot see how anything I have done could cause these problems.
For giggles, I took -g off of the compiler call, and to my surprise, the window with "Start" appeared, and then the Gtk screen from Glade appeared looking good for something executing for the first time.
So maybe this needs to be turned into an error report on bad information being generated by -g?
There is no easy way to turn this large program into anything smaller to test.
Wally G