Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28502 Discussions

No debug possibility with VS Professional 2033 (17.7.3) and Fortran 2023.2

Matthias_Schumacher
1,441 Views

No watch points, no exam of variables, endless indexing of source and consuming memory as max as possible. 

It is all after updating to the new VS version.

I reinstalled  VS and Fortran. No positive effect.

 

Any hints appreciated!

Kind regards

 Matthias

 

0 Kudos
13 Replies
Steve_Lionel
Honored Contributor III
1,425 Views

Roll back to an earlier VS version - Microsoft broke things - again. A future Intel update will address this.

0 Kudos
JohnNichols
Valued Contributor III
1,407 Views

I tried this yesterday.  It appears you can only roll back one version of VS.  If you have 17.7.3, you cannot get to the Intel required version in community.  

As noted elsewhere the cadence is not even close to being togethor, and depending on when Intel adjust the next release the new version may be using a version of VS that will be out of date by the time Oneapi is released. 

If I wait to get VS that matches the next one-api, it may have been superceded by later VS releases and still be unavailable.  

Surely Intel knows months in advance which version they used.  It would help to publish this well before the release.  

This is not just Microsoft's fault. 

0 Kudos
Ron_Green
Moderator
1,391 Views

Actually, Intel gets the same VS previews and releases as everyone else.  No special treatment.  17.7.0 Preview tested OK, but obviously the 17.7.0 Release was a surprise.

 

We are investigating ways to patch this, or create a whole new Fortran Compiler Patch Release.  We understand the inconvenience.  

 

ron

0 Kudos
Ron_Green
Moderator
1,385 Views
0 Kudos
JohnNichols
Valued Contributor III
1,382 Views

I am not complaining, I am well aware of the problems of communication.  I was merely wondering if the team who is fixing the current version could warn us what version not to go past as we approach the date of your release. 

A simple stay with 17.7.13 would be nice, note would be nice.   

Otherwise we soldier on and just enjoy life and reading this forum. 

Thanks for the reply, it must be a pain watching this site all day.  

I still fail to see why you all let Steve retire, he is always on this site. 

0 Kudos
Steve_Lionel
Honored Contributor III
1,378 Views

@JohnNichols wrote:

Thanks for the reply, it must be a pain watching this site all day.  

I still fail to see why you all let Steve retire, he is always on this site. 


Always? No. I've been traveling a lot more, for weeks at a time, and recently returned from three weeks in the Arctic. Trust me when I say that I never once looked at this site during that time. A big difference is, as I put it here, I don't feel obligated to respond to every question. I will help where I can. Ron, Barbara, Devorah and the others on the support team are doing a fine job without me.

53146735893_73d94ce8c3_c

 

Ron_Green
Moderator
1,375 Views

We had/have an amazing mentor!  

Matthias_Schumacher
1,338 Views

Thanks very much for the quick response, especially to Lionel (Enjoy your holiday!).

I wait for some time and maybe go back to 2019 (I'm not allowed NOT to use the newest version of VS 2022)

 

Kind regards Matthias

0 Kudos
JohnNichols
Valued Contributor III
1,217 Views

Excuse the 60's slang I am from that era. 

This is why I prefer to work for a small company and look after the IT.  I do not make silly rules that keep the IT people employed. 

Example from old :  No, you may not have VS on your computer.  Why -- we have not tested it?   What?  -- follow the rules

How to break the rules --   lol there are many ways, just do not get caught.   Of course if you work for the gov - follow the rules those guys have no sense of humour. 

But looking after 1000 computers you need some rules.  

I was at UIUC and the IT people had the best equipment, I would go over and ask to use it.  Sometimes the four people would all be out and being a nice guy, like Steve, I would answer the questions, I have done IT since '86 so it was usually simple.  Try unplugging it - got rid of a lot of people. 

One day Earl the IT director comes up and gives me a key, normally no one else is allowed in, but you are special you save us a lot of time by answering stupid questions and everyone thinks you are one of us.  Ok. 

A few months later, new IT guy comes over, it is  lunch time, you have to leave so I can lock up. 

Ok.

We leave, I walk around building and let myself in. 

An hour later guy comes up to me and says, Earl says to apologize, you are special and do not have to follow the rules. 

Next university, I could not afford Powerstation, it is sitting in the IT office, they keep door locked.  I notice the poor lady has to carry the new monitors up two flights of stairs, this is the old monitors that weighed a ton, so each morning I went to the delivery office and carried up the stuff for her.  No sweat. I left it outside the door. About a week in she says, I am giving you a key can you put them on my desk.  No sweat. Saturday I raid the office get Powerstation, load it onto the my work computer and return disks.  I carried that stuff for several years, it was worth it, although Powerstation was a dog of a program. 

As Frank Burns said - It is nice to be nice to the nice.  At the moment, this is one of the few nice places in the world, although why some one would choose the Artic over Hawaii is beyond me.  Where else can you get spam hamburgers?

 

0 Kudos
Matthias_Schumacher
1,247 Views

Hello community!

 

Where can I see, if compiler engineering has accepted the error and will focus on that problem?

 

KR Matthias

0 Kudos
Ron_Green
Moderator
1,226 Views

The bug ID is IGDB-3970.  If you reported this on the Online Service Center with your Priority Account, you will receive updates from your assigned Technical Consulting Engineer. 

If you have not reported this, or do not have an active Priority Account, you can check progress here.

 

Monday was a US holiday.  Friday was an Intel holiday.  Before the end of last week, we escalated this to our debugger team.  Understand that the Fortran Expression Evaluator comes from our debugger team, not the Fortran team.  

 

We have escalated this and we are actively tracking this with that team.  There is a redesign of the FEE that allows this plugin to work with VS after they removed the API we were using in the past.  I did mention that MS does not inform us of API breakage between their minor updates.  We caught this in Preview testing.  But it was a api break so significant that coding changes had to be made to use a new API to enable the FEE.   And that has to be tested, pass regression tests and QA/PV tests, security scans, code reviews, etc.  

 

We understand the impact of this bug.  And we are working on a fix.  We will post notice when we have a fix.

0 Kudos
David_DiLaura1
1,206 Views

I updated my copy of VS last Friday. Would that I had checked the forum First!

VS Roll-back took me (way) back to release 16.6.  Geez.

Ron_Green
Moderator
1,172 Views

@David_DiLaura1 @Matthias_Schumacher  we may have a temporary workaround while we prepare our integration kit.  

Try this:

A quick workaround is to disable “Load debug symbols in external process (Native only)" in the debug settings window.

 

vs_debug_workaround.png

 

0 Kudos
Reply