My application has 421 files of javascript code. When i scan them using fortify v4.30 , auditworkbench (.fpr) report shows that only 29 files of .js code has been scanned. Is there limitation on fortify for scanning some types of .js code? If yes, what types of .js code is not supported by fortify? Thanks in advance
Fortify should scan all of it.
When you open the fpr in auditworkbench, click the "Build Information" tab under the Project Summary to see what was scanned and what might have been missed. Perhaps you missed a directory by accident.
If you want more assistance, tell us specific details about how you are scanning.
Related
I have an application that depends on a third party library where a file starts with sign '$'.
I have read about this issue, which is discussed in this thread Visual Studio Online TFS refuses to "source control" filenames starting with $
Apparently there is no solution - but i really need a solution.
Does someone have a workarround to this or any ideas on how to solve it?
The thread is more than 2 years old so maybe something has changed that i do not know of :)
Thanks.
Still not changed. Files and folders you add to Team Foundation version control must conform to the following restrictions:
Source Link: Version control files
Files stating with $ such as $xxx.dll will auto change to xxx.dll when you checked in TFS source control.
In other words, you could not keep files stated with $ characters in TFS source control system. If you force rename a file already in source control, you will get a pop up error such as below screenshot:
I'm afraid the only workaround is renaming the third party library file.
I have a new project need create auto test script with ios application, but only can provide ipa file (developer build), cannot provide source code. Currently I used Tuneup JS. I have some questions need help. Please see details as below.
I only have ipa file no source code, so how to get application elements and how to locate element? Is there any documents can reference? If can provide some examples should better.
If this ios application is HTML5 application, can automate?
When I use Tuneup JS to create script is there any recommended IDE to help create script? Because very hard to remember all APIs.
very very appreciate for your helps.
Thank you very much
You can use window.logElementTree(); and in the instruments window, when you run the app, it will log the elements of the current window.
check out apple's documentation:
https://developer.apple.com/library/ios/documentation/DeveloperTools/Reference/UIAutomationRef/Introduction/Introduction.html
Your second question makes no sense.
I use sublime text editor to write my tests, although it isn't an IDE, just a fancy text editor.
I cannot seem to locate the .pdb files after I have created the OpenCV binaries; using Cmake and then building the OpenCV solution using VS2013. Any help?
As Martin Suggests in the comments above, see
Visual Studio 2010 not generating .pdb files
Plus different versions of OpenCV generate the files slightly differently. Search for .pdb files where you had compiled your OpenCV solution.
This is not the answer for this specific question, but since I did not find the solution and question took about it, I write it to this thread. I hope it may be useful for other fellow sufferer.
My problem was that I could not reach a subset of code in Debugging. During the Debug mode it told, that "The breakpoint will not currently be hit. No symbols have been loaded for this document", which is a well discussed problem. But the base problem was, that I could not even find a .pdb file, which should have been loaded, to reach that code. The problem was, that the Build properties of the project has not been set correctly.
To ensure, that you project generates the .pdb file, check the Build settings of the project:
Right click on project -> Select "Build" tab -> In the "Output" section click "Advanced..." button -> At "Debug Info:" dropdownlist select "full" option.
We just set up TFS 11 for the first time. Running a gated check in, it succeeds but returns this message:
'srctool.exe' returned an unexpected exit code: '-1'. An error
occurred when opening a file "CustomDllName.dll": Assembly
"CustomDllName.dll" is not a valid .NET assembly and will be skipped
for analysis.
Well, it's right: that file is a legacy Visual Basic 6 DLL that we don't have much control over. It's included in the project for COM access to some of the methods.
Is there a way to instruct srctool.exe/TFS to skip that file when doing the inspection? Or another way to attack this?
Here is the solution that ultimately worked for me
A member of the TFS 11 team at Microsoft mentioned to me that the problem is due to a change in behavior that the Windows 8 team made to the srctool.exe tool.
By copying this file from the Windows 7 SDK (WinDBG) toolkit and overriding the one included in TFS 11 Beta, I was able to successfully run a build without any errors.
Is this a srctool.exe error from the shipped IndexSources activity? srctool.exe in this activity does one thing, which is to list the source files information in the pdb. I am not a srctool expert so I don't know why it fails in this case. I do know that srctool.exe has some behavioral changes in version 11, most of those are fixes from the previous version.
There is a workaround which requires udpating the build template. It is not very nice but it works. Srctool.exe is run (inside IndexSources activity) for each pdb file in the SymbolFiles collection. Now that you know which pdb fails, you can update the build template to add a RemoveFromCollection activity before the IndexSources activity that remove the troubled pdb from the SymbolFiles collection. This is by far the most straightforward workaround I can think of.
Alternatively, you can edit FindMatchingFiles activity's search pattern to exclude the pdb files you don't want to have sources indexed.
Based on the error message you got, it doesn't seem to be related to the known issue Ed mentioned. We fixed this issue for the next release, so if it's related, it should be fixed :-)
Let me know if you have any issue with VS11 Beta around the build templates.
Thanks.
I am debugging a bpg with multiple dll's. Can someone tell me why my breakpoints, that DO work, eventually stop working? The only way to get them back is to do a build all in my project group file (BPG file in Delphi 6)?
I have looked at several other posts, but have not had much luck getting an answer to this specific question. Again, I can successfully debug, all dll's in the BPG provided I do a build all. Doing a build all every time is taking too long.
I am using Delphi6 in WinXP.
Thank you
In Delphi 6, such a failure to find debug information (all the blue lines are gone from your sources) that is solved by a complete rebuild is usually a symptom that you have to examine your project (.dpr) settings. For each project (dll or exe) make sure a different unique compiler output folder (DCU output folder) is used.