forums.silverfrost.com

[Fabio]

I'm using Windows 11 and till yesterday, all the features of Plato and compiler where OK. Suddenly I got a trouble with the SDBG and after many attempts and re-installation, I couldn't solve. Independently from the compiled object, at the "write(*,10)" statement I'm getting an error the following exception: 0xE06D7363. The code works fine if launched with "Start run".
Gratefull in advance for any advice.
[/img][/code]

[wahorger]

A small sample of your code that duplicates the problem would be helpful.

Also, 32-bit or 64-bit?

I found this on-line:

[PaulLaidler]

Also, if you are not already doing so, use /CHECKMATE on the FTN95 command line when debugging.

[Fabio]

Many thanks for reply: this simple code is enough for test the issue on my system

winapp
program test_write_statement
implicit none
!
integer :: i=76

!
write(*,10)i
10 format('Test of statement ''write'':',i2,'Stop')
!
stop
end program

Remarkably, the problem disappears if I remove the "winapp" condition.
I could insert a snip of the screen but I need help to understand how to use the "Img" control in the post (sorry, this is just my first post).

Cheers

Fabio

Fabio

[Fabio]

I add here more details about the exception:

- I'm using Plato as IDE
- The problem appears in 32-bit or 64-bit
- /CHECKMATE as no effect

Fabio

[PaulLaidler]

Fabio

Your test program runs OK for me (both Win32 and x64).

Please state your Windows version and check if there are any pending Windows updates to your system.

[wahorger]

This has been my experience, on and off, when using the WINAPP directive.

Sometimes, you'll get an exception or odd run-time performance when you've used WINAPP, but it is NOT supposed to be a windows application.

I've never been able to identify what causes it. My commercial application is for windows BUT one of the apps runs in a command window (not a windows app), and it would act strangely if I used WINAPP.

I decided to use WINAPP only for the main routine of the individual windows applications, leaving it off for the one command window program. No problems.

[Fabio]

Thanks for support: now I'm using the debugger without the WINAPP directive... is not a big issue.

The version of my OS is Windows 11 Pro, version 23H2 (build SO 22631.3085)

[wahorger]

Glad this was of some help!

I've never used the debugger. Perhaps because I'm too lazy, or because when I started using FTN95, I had a product that was working with different systems and I wanted to port it over. Most of the issues I've had over the last decade have been of my own making OR a deficiency was identified, and Paul and the crew worked out the fixes.

Eons ago, I learned assembly language using the listings and reference cards for the IBM 7040 I was using at university. Then, on the IBM 360 series. No debugger on either platform!

On the PDP-8E (circa 1972), however, I used the debugger because it was easier to get a program to load/run if I loaded the debugger and manually typed the hand-assembled code!

Ah, those were the days!

[PaulLaidler]

If it is a simple program then the switch to 64 bits might be seemless and might fix the problem. From Plato select x64 on the toolbar.