We are trying to run shark on our iphone application. However, in the analyzed samples it does not list any of our application function. All that is listed are the libraries and when we click on any of those, the assembly code is visible.
Most of the sites mention about 'Generate Debug Symbols' option when building the app; I am not able to find this option either. Instead I have enabled the 'Generate Profiling Information' option.
Can anyone please help as to how do I see my application functions and source code in the analyzed samples of Shark?
You have to compile it with for debugging (not just with symbols), see the shark manual.
Related
I have the project which uses my second project as a lib. I see that them two has optimization level for debug none -o0 and for the release fast -0s
but in spite of this in the log, I see such a message
... was compiled with optimization - stepping may behave oddly; variables may not be available.
What are possible ways to fix it?
P.S. should be mentioned that debug doesn't work. It stops on the breakpoint, but I don't see the values of variables.
UPD
my second project - it is a lib. The structure looks like this
Demo - is a project
Lib - is lib
Let me know if I missed something
The build settings are tied to configurations. In your build settings for optimization, the Debug configuration is set to nonoptimized, and the Release configuration is set to optimized.
So far, so good.
But which configuration are you actually using when you build? That is determined by the scheme. Use the Scheme Editor to look at the schemes for your different targets. (You will have to look at them one at a time.) In each, look in the Run action. It says which configuration to use. If the pop-up says Release, change it to Debug.
Is it possible to disable WARNINGS (text in red) for the Output window, and only allow it to report errors?
I try a bit with the settings, and according to other posts I set Quiet for the Ant, and option -q for Maven, but it has no effect whatsoever.
So can anyone tell if it can be done at all, and if so, how, please?
From what I see the warnings are generated by the program you execute (or maybe by a library used by your program).
Ant or Maven are build tools to generate your program, that's why changing their verbosity level won't impact the program output.
You should check if your program accepts some command-line options, there might be one to adjust the verbosity level.
EDIT: just had a look at "aparapi", I see that it's a library, so you should check the library API if you can configure the verbosity level, or if you can redirect log messages to a file.
Can anyone explain these three debug symbols on VSCode I have found on the internet?
My vs code has the one with the play icon.
All demos online on debugging have the one in the middle. How do I get that?
Also, node js debugging is installed but I think it shows as disabled, with no option I can find to enable it.
To answer your question directly [TL;DR]: you already have it if you are using the latest version of vscode. It will take you to the same view as the one on the right
If you look at the codicon libray ref the middle one you pointed out is not present.
Visual Studio Code made changes in February 2020 ref that incorporates running and debugging to be something more harmonious:
User studies revealed that new users have difficulties finding how to run their programs in VS Code. One reason is that the existing "Debugging" functionality is not something that they relate to "Running" a program. For that reason, we are making "Run" more prominent in the UI.
The main menu Debug has become the Run menu.
The Run and Debug view has become the Run view and the corresponding Activity Bar icon now shows a large "Play" icon with a small "bug" decoration.
So in other words, there is no difference. The 'Run' and 'Debug' view is synonymous and the icon reflects those changes. As they noted, the Debug view is now called the 'Run' view, but it still offers debugging and breakpoints.
There are 2 possibilities you are running into however:
The tutorials and guides you are using are out-dated (showing an outdated version of vscode)
The tutorial or guide is using an extension that offers debugging capabilities. Extensions have some control over the icon you see
The extension is for single file debugging, according to the June 2020 ref notes, vscode recommends the following:
For debug extensions that want to improve the single file debug experience by adding a "Run" and/or "Debug" button to the editor, we recommend following these guidelines for a consistent look and feel:
Contribute Run and/or Debug commands in the package.json (see Mock Debug):
Use the command titles "Run File"/"Debug File" or "Run Python File"/"Debug Python File".
Use the $(play) icon for Run and $(debug-alt-small) for Debug.
Where their codicon library was updated in June to reflect the following:
As you can see, none of them are prefixed with verbiage like 'run', but they all represent the same functionality.
Additionally, you may see this icon as well:
This represents the panel (view) where the output of your debug will go.
I've read this article about analyzing runtime performance. The image below is copied from this article. If you check this image, there are yellow highlighted execution time hints for JS files next to each line in the file.
I find this line level profiling feature pretty useful and I would like to try it in my own projects, too.
However, when I open a JS source file in the sources tab, I cannot see it. Note that, I already took a performance profiling snapshot. But still I cannot see this execution time hints.
How can I reveal this feature?
Thanks.
it's seems that it's removed to new tab.
you can try this:
open javascript profile tab (or ctrl+ shift + p on win and type javascript profile)
start to record the site and refresh
stop the record
click on one of the js file
enter image description here
you got exactly what you need
enter image description here
I wasn't seeing the line by line timings from the profiler either, and it was driving me crazy for days.
My code was written in typescript and converted to JScript with source maps using esbuild.
When I turned source maps off in esbuild, the line timings reappeared from the profiler!
The Jscript is close enough to the Typescript so the line timings are still useful.
I could have sworn I'd seen it work with source maps in the past but now I'm not so sure. It would be great if the line timings did work with source maps but it kind of makes sense that they don't.
Has anyone else seen profiler line timings work on code with sourcemaps turn on?
I'm attempting to program very basic VHDL on eclipse using the Sigasi plugin with an educational license - with the aim to be, I can program a simple entity and a test bench for it, then compile and simulate it in Xilinx's ISim.
I have installed Eclipse, Sigasi & Xilinx ISE Webpack, and have attempted to add the ISim toolchain to Eclipse as shown in the Sigasi website here
It appears okay but it says I need to "activate" the toolchain (as shown below)
However, when I follow the "click here to activate now", I get taken to the scree below - from which nothing happens. If I click Apply, nothing happens, there's no further options!
My question - how do I actually configure ISim to launch from Eclipse, is what I want to do actually possible or have I misunderstood and if so, how do I do it.
Thanks very much for your help!
David
When you enable the ISim toolchain, Sigasi will automatically compile your files with ISim when you save your files. You can check the output in the Console View
To start a simulation, you need to set a top-level first. You can do this in the Hierarchy View. Next, click on the Simulate button.
You can find more details in the Sigasi Studio manual