Vista support

I haven't checked yet, but has verion 5.00 been tried out on Windows Vista at all (as a development environment - compiled programs certainly don't seem to have a problem running on Vista) ? I had a go with 4.91 but sdbg crashed on startup. I realise its early days, epecially as MS don't claim proper support even for VS 2005, but I just wondered what the official line was...

Thanks, Alan

As yet no tests have been carried out using Windows Vista.

There have been some tests performed with Vista Release Candidates and they did not show up any problems (although this was before the VS2005 support was complete). I will be doing more complete tests with the Vista RTM shortly.

Just given it a go on the RTM - it looked promising at first - a very simple win32 program worked and debugged. Unfortunately anything a little more complex (maybe when using clearwin) crashes sdbg in the same way the 4.91 did during debugger startup:

Access Violation The instruction at address 10047083 attempted to read from location 11e90994 1004704c module::search_map(<ptr>constÄchar) [+0037] 10002110 wait_for_pause(int) [+0486] 100078d2 sdbg_main [+0cef] 00401000 main [+0076]

😦

As silverfrost pointed out 4.91 was tried on the Vista RC's and was OK with respect to the compiler and Visual Studio. The tests concentrated on looking at Visual Studio integration (although only with 2003 at that stage, although there is no reason to think 2005 will not be fine). It may be possible that with the final release of Vista there may be work to do in other areas.

I have tried sdbg on a substantial example and seen the same error message. What is odd is that it has nothing specifically to do with Vista and is caused by DLLs being relocated at load time -- specifically ones produced by FTN95. I can reproduce it on my XP setup now and can email you a replacement sdbgdll.dll to try.

That said... relocations of DLLs are common and although the issue looks cut and dried I cannot believe this has been an issue since SDBG version 1.

Does FTN95 v5.01 support VISTA? What about the Debugger (SDBG) and ClearWin?

No there is no guarantee that the release will work with Vista. No doubt some things will work. But there will be issues as yet unresolved.

Paul, Is Vista support (for development/debugging) something you guys are looking into at the moment at all ? Any very rough guesses as to when it might be supported... ish ??

Thanks, Alan

Some tests have already been carried out on Windows Vista. I expect that the next full release of FTN95 will support .NET 3 but no date has yet been set.

Speaking as someone who is only doing Win32/ClearWin development, any point-releases or fixes that sort out the Win32 debugger problems would be greatly anticipated 😃 although I appreciate it's not likely to be top your list at present...

Quoted from Robert I have tried sdbg on a substantial example and seen the same error message. What is odd is that it has nothing specifically to do with Vista and is caused by DLLs being relocated at load time -- specifically ones produced by FTN95. I can reproduce it on my XP setup now and can email you a replacement sdbgdll.dll to try.

That said... relocations of DLLs are common and although the issue looks cut and dried I cannot believe this has been an issue since SDBG version 1.

... this seems to have been ignored...

It is the only Vista specific problem we know about

Great, okay I missed that reply... I would love to try a replacement sdbgdll.dll to see if it works - if it can be emailed to me or put somewhere for download I'll give it a go !

Cheers, Alan

Robert,

Thanks for the email - the updated sdbg seems to work fine on Vista - yippeee!

Now, any chance of a new sdbg.vs.dll for Visual Studio 2005 😃 ? I'm surrently on VS2005 SP1 and attempting to debug Fortran using the integrated debugger (Win32) makes it cough up blood in typical Visual Studio fashion and crash.

Thanks again, Alan

Hi Guys,

I'm still on the Vista trail I'm afraid 😄 - some info on whether there is likely to be a short-term fix to the VS2005 sdbg.vs.dll in a similar vein to the updated sdbg would be greatly appreciated, even if it's a 'not for a while'.

Thanks. Alan

If you mean the DLL relocation problem (i.e. the same problem as SDBG) then we can provide a DLL to test.

Robert,

I do indeed mean the relocation problem - yes please I'll be happy to test it - just send it to me in an email and I'll check it out.

Thanks, Alan

Robert,

Thanks for the update. I think it's a big thumbs up 😃 I say 'think' because initially I had problems with programs hanging when bringing up some clearwin windows (%di and %ww), but I've now installed the VS2005 SP1 Update for Vista Beta and it all seems to be working fine - maybe a little slower than under XP but working just the same. If I find any problems I'll let you know.

Thanks again, Alan

Quoted from Robert I have tried sdbg on a substantial example and seen the same error message. What is odd is that it has nothing specifically to do with Vista and is caused by DLLs being relocated at load time -- specifically ones produced by FTN95. I can reproduce it on my XP setup now and can email you a replacement sdbgdll.dll to try.

That said... relocations of DLLs are common and although the issue looks cut and dried I cannot believe this has been an issue since SDBG version 1.

I have Vista on my new computer and can not run SDBG anymore because of the error message. I would be very happy to get that sdbgdll.dll too. Thanks!

There is an interim build here: http://www.silverfrost.com/public_downloads/debugger.zip