Problem with SDBG

Last Monday I replaced my Version 5.5 installation of FTN95 by Version 6.0. Now I get difficulties using SDBG:

• I define a breakpoint somewhere within the program (F2).
• I start the program (F6).
• The program interupts at the breakpoint.
• When moving the cursor to the source code window the program resumes.

Is it a known problem?

Preparing this topic for the forums I am just performing some tests:

1. I created a simple program. SDBG works properly
2. I inserted a 'winapp' statement after the program statement. SDBG continues when entering the source code window.
3. I modified 'winapp' to '!winapp'. SDBG still continues when entering the source code window.
4. I modified '!winapp' to '!winxapp'. SDBG still continues when entering the source code window.
5. I modified '!winxapp' to '!wxixnxaxpxpx'. SDBG works properly.

A little bit strange?

First make sure that you are using the salflibc.dll that comes with the 6.0 release. If there is an old dll lying around that is getting in the way then this will make a difference.

saldiag.exe in the compiler folder will help you to find the salflibc.dll's on your machine.

I have the same problem with version 6.

I have two salflibc.dll libraries, both version 12.10.30.21 date modified 30/10/2010.

What version should we have with Version 6.0?

Sorry, I think you are right. I have probably fixed this regression since the last release. I will check this out and see if we can make a new salflibc.dll available for download.

Any chance of a file being made available since the debugger is unworkable as it is.

We are working on this. There will probably be a new release very soon. The current version should not be 'unworkable', however if you can get hold of and use the previous salflibc.dll, this will probably work OK with the latest FTN95.exe. Failing that, use the previous salflibc.dll only when running the debugger.

Quoted from PaulLaidler We are working on this. There will probably be a new release very soon. The current version should not be 'unworkable', however if you can get hold of and use the previous salflibc.dll, this will probably work OK with the latest FTN95.exe. Failing that, use the previous salflibc.dll only when running the debugger.

Thanks Paul. I shouldn't have said 'unworkable'. Its more an irritation. I am using the free version at home and have a full licence at work. Both are on version 6.0

I managed to extract an older salflibc.dll from the install package for FTN 95 express (I have an old copy but last time I looked the download wasn't version 6.0 either) so I will see if that works with my personal copy.

If anyone else wants to do this here are the steps:

1. I ran the install just to unzip everything but quit when it said install, repair remove.

2. Extract files from the MSI file by typing at the command line:

msiexec /a 'Silverfrost FTN95 Express.msi' /qb TARGETDIR=c:\Salford_tmp

3. Found the salflibc.dll and copied it to my Silverfrost install folder.

Looking forward to seeing the new release too.

David.

I would like to come back to the original problem in application of SDBG. Meanwhile I can localise the problem better.

When starting SDBG I get a a menu bar and another bar with icons for usual command below. When moving the mouse pointer from the source code window to the icons above, the corresponding functions are executed immediately. I would expect that functions are executed by mouse clicks on the corresponding icons.

Usually I move the mouse cursor between source code window and menu items. Then I have to pass the icon bar and thereby activate them with unpreditable effects.

Is this problem known or is it specific for my installation?

Today I am aware of the behavior and come along with it. However, it is irritating and inconvinient.

This (mouse hover) problem is a regression in the salflibc.dll that goes with FTN95 v6.0. It will be fixed in 6.05 that is planned to be released very soon.