forums.silverfrost.com

[saturn]

When attempting to run an app compiled with DEBUG, CHECK, UNDEF OR CHECKMATE in SDBG it attempts to start in SALFStartup with Call Stack/Status message: Program Breakpoint.

I am using WinXP beccause starting SDBG in Windows 7 is very problematic and unreliable.

Any ideas what the problem is?

Thanks

[PaulLaidler]

If I am understanding this correctly then what you are experiencing is the designed behaviour for SDBG. When running SDBG directly, by default it will stop at the first executable statement to allow you to step through code or set break points and select "Run".

There are ways to over-ride this behaviour and if you start SDBG from Plato then you have the option of running directly to a selected break point (probably other options as well).

In some contexts SDBG will be launched when you simply run the executable (compiled using one of the debugging options). This can occur when the executable encounters a run time error.

[saturn]

Paul,

Thanks a lot for your prompt reply.

How can I bypass the behaviour of it stopping in SALFStartup when running SDBG directly?

I always run SDBG directly and most of the time it starts in a routine with debug information rather than SALFSTARTUP. I then set breakpoints.

Thanks.

[saturn]

no message

[PaulLaidler]

Sorry I missed the reference to SALFStartup.

This is an internal function within salflibc.dll without debugging information so I don't understand how the debugger can break at this point.

[saturn]

It tries to break into SALFStartup but can't since there is no debug info as you mention. SDBG doesn't progress further.

It does it intermittently. Not sure why.

I am sending an email with screenshot of SDBG.

[Robert]

Is it possible you have mismatched Salflibc.dll on your machine? For example, you might have one in the application directory and a different one elsewhere on your path.