As the title says since the last VM upgrade there appears to be no disassembly window. The appropriate parameter is set in VS2019 in the project settings is set to true.
The output window claims it is producing a disassembly listing but there's no window in the drop down list.
It also refers to a log file for details somewhere deep in the app data folder, but when navigated to it is 0 bytes long.
Any ideas?

Thanks for the response.
The listing isn't there for either the mega board or the Due. I'm in the process of transferring a project from the mega to the due and that's when I first noticed it was missing.
Regards

The latest release (20.07.08.9) has improved logging around the Disassembly View generation, and it will expose the command line to run the process manually if there is an error encountered.

Available at the top of this board: https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

The latest release (20.07.08.9 and above) has improved logging around the Disassembly View generation, and it will expose the command line to run the process manually if there is an error encountered.

Available at the top of this board: https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Thanks, as you can see we are asking objdump.exe to write the results to the file and it is failing, producing a zero byte file.

4.8.3-2014q1\bin\arm-none-eabi-objdump.exe"  -h -S -l ug\Due_coil_winder.ino.elf" > "C:\Users\Blah nder.ino_objDump.log" 

Can you please take the command that you see without the cmd.exe part (see above) and open windows cmd then run it. See if we gate the same issue.

I notice we have an extra " at the end of the entire command instead of a quote around the .exe, which we will remove in the next release, however it doesn't cause it to fail for us. I have corrected that in the example above.

This might also be the length of the file names or a long path issue. We can try to replicate that and convert to short 8.3 windows paths if that is the issue. 

You can test by changing the output .log path to somewhere shorter. The output .log paths is

"C:\Users\Blah nder.ino_objDump.log"
 

You will also see similar for the .elf that is produced the dump from. You can copy the elf to the same simpler path and then change the elf path in the cmd

"C:\Users\Blah  nder.ino.elf"
 

As you can see it is a simple external command. If you have time to make these tests and narrow down the issue that will be helpful but we will be able to look at it some more towards the end of the coming week.

Thanks

I think I have found the error, the syntax for the command string has a missing " after the path to the application. Maybe that's where your extra " came from at the end of the string?

This works from a command prompt:

"C:\Users\Blah q1\bin\arm-none-eabi-objdump.exe" -h -S -l "C:\Users\Blah l_winder.ino.elf" > "C:\Users\Blah l_winder.ino_objDump.log"

The syntax appears to be: "Path to application" switches(-h etc) "Path to elf file" > "path to output file"

Hope that makes sense?

Update;
Managed a temp fix by putting a single " in the disassembly switches section of project properties

We have published an update containing the fix detailed above, 20.07.08.12, which is available from the top of the below board:
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Let us know if you encounter any further issues, and thanks again for the great reporting!

Well it has quit working and gone back to just listing the mile long path to the .log file. 
If I run the string in a cmd window, it automatically opens a notepad window and populates it with a massive file of unintelligible gobbledygook. 
Closing Notepad results in a 0 byte long .log file being saved in the appropriate directory.
As I mentioned in the previous post the optimization settings did have an effect on the creation of the disassembly listing. This is no longer the case as it doesn't work with any settings.
I would suggest that the file is now bigger than Notepad is capable of opening

I appear to be missing something as I do not see anything in yellow on this page!

Using Chrome