I'm using GPS IDE for Ada 95 coding. When I try to put a break point in a .adb file, I'm getting a message "No source file named filename.adb". I built the project and initialized the debugger. What could have gone wrong?
Oddly, I'm able to execute the program.
Did you enable the debug option for your project? Use Project/"Edit Project Properties" to open the project properties dialog, click the "Switches" tab. Then on each of the Gnatmake, Ada, and Ada Linker tabs check "Debug Information". Close the dialogs, then do a Build/Clean and rebuild your project. (Don't forget to save any changes, do Project/Save All.)
Related
I installed the last Qt 5.12.2 . Then I open the cmake project via Qt Creator.
First I see a huge count on the intellisence issues: from "udeclared identifies of nullptr" to errors with each type "unknown type name".
The build proceeded successfully and I receive correct binary.
But any breakpoint marked as "Unclaimed breakpoint" and I cant debug any .qml (the .cpp could be debug)
So why it happens and how to debug the QML? (this future is still supported?)
UPDATE: The "QQmlDebuggingEnabler enabler;" and "doc.qt.io/qt-5/qtquick-debugging.html" doesnt helps :(
UPDATE2: #Amfasis -
I created a CMake-based Qt Quick project, and it shown that it supports QML/JS debugging. I checked the CMakeLists.txt, and found one relevant line:
target_compile_definitions(${PROJECT_NAME} PRIVATE $<$<OR:$<CONFIG:Debug>,$<CONFIG:RelWithDebInfo>>:QT_QML_DEBUG>)
So I think if you'd like to debug your CMake-based Qt Quick project, you should also add this line to your CMakeLists.txt.
And don't forget to check on enable QML in the project setting within the sector of debugging setting.
I would like to add the extern jar library commons-jexl-2.1.1.jar. I copied the jar into the libs/ folder and performed the Add as library... menu point. I don't receive any errors in the code and everything seems to work but when compiling and starting the application I receive the error java.lang.NoClassDefFoundError: org.apache.commons.jexl2.JexlEngineon this line private JexlEngine jexl = new JexlEngine();
Does anyone know what I've missed?
Unfortunately, that menu command is doing the wrong thing for Gradle-based projects, which I assume yours is. (Gradle-based projects are what you get when you create new projects in Android Studio). I've filed bug https://code.google.com/p/android/issues/detail?id=62249 to request implementing this menu command properly for these projects, or at a minimum disabling it until it's implemented to prevent confusion.
In the meantime, you can add external JAR dependencies by going through the Project Structure dialog, which will add the appropriate entries to your build.gradle build file. Choose File menu > Project Structure, and click on the "Modules" entry on the left. Choose your module from the middle list, and click on the Dependencies tab on the right. Then click on the + button at the bottom to add a new dependency. Screen shot here:
The + menu has an option for "File dependency" (pictured). You will get a file chooser that will let you select the jar file.
If your dependency is one that can be found in Maven, you may find it more convenient to specify the Maven coordinates; that way, the build system will automatically download the dependency, and you won't have to download and store the JAR manually. To set that up, choose "Maven dependency" from the + menu. You'll get a dialog where you can search to find the proper Maven coordinates for your library. In your case, those coordinates will be "org.apache.commons:commons-jexl:2.1.1#jar"
If you prefer to edit build files by hand, check out your build.gradle file after completing the Project Structure dialog changes to see what it did.
The docs for using Gradle in Android are at http://tools.android.com/tech-docs/new-build-system
courtesy The App Chaps
I've been struggling with the same thing for many hours, trying to get the Gson jar to work no less. I finally cracked it – here are the steps I took:
Put the Gson jar (in my case, gson-2.2.4.jar) into the libs folder
Right click it and hit 'Add as library'
Ensure that compile files('libs/gson-2.2.4.jar') is in your build.gradle file
Do a clean build (you can probably do this fine in Android Studio, but to make sure I navigated in a terminal to the root folder of my app and typed gradlew clean. I'm on Mac OS X, the command might be different on your system
After I did the above three, it started working fine. I think the 'Add as library' step was the one I'd previously missed, and it didn't work until I cleaned it either.
[Edit - added the build.gradle step which is also necessary as others have pointed out]
I'm trying to run a very simple program that just closes the window when clicking the `exit button, but get the following output provided that the application window that contains the button does not show up:
Starting C:\Users\Ola\Desktop\signal_slot1-build-desktop-Qt_4_8_1_for_Desktop_-_MSVC2008__Qt_SDK__Debug\debug\signal_slot1.exe...
Qml debugging is enabled. Only use this in a safe environment!
What should I do in this case?
You have enabled QML debugging (actually it's on by default), this opens a port to the Javascript interpreter that is running the QML so you can get debug output from it. Obviously this creates a security hole, so it should be turned off when not being used in safe place (it's turned off automatically when you release compile). This warning is to remind you of that.
If you are not using QML, turn it off anyway. You can turn it off in the project's options page, where the build settings are (it's a check box in the qmake area).
Assuming you use Qt Creator:
If you select the Release-Build type the QML debugging will be disabled. To do this, select the build type on the bottom left corner above the "run" button and choose "release".
Manually, there is an option passed to qmake (either in the .pro file or via command line arguments) named
CONFIG+=qml_debug
which enables qml debugging.
If you omit that, it should be disabled.
You can change it to release mode if you want to and that would solve the problem
but I recommend you to change between MSVC and MinGW and check which one is going to work.
Project->Build and Run-> and choose what you need.
I am trying to figure out how to debug in VS using the TFSBuildServiceHost.exe method, here is the article about this: http://blogs.microsoft.co.il/blogs/baruchf/archive/2009/07/02/debugging-team-build-now-you-can.aspx
I am not able to get this working. First off, my machine does not have a TFSBuildServiceHost.exe running. So I tried to do this on my team foundation build server and I found the process. Great so I open the workingflow script, set my breakpoint, attach the process. Then what? The article says "Run the build." How? There is no run button...
So instead I went to my team explorer and right clicked the build and run it, but the breakpoint does not get hit. What am I missing?
If I look on the breakpoint window I see my breakpoint but it has a warning symbol that says "this breakpoint will not currently be hit. No symbols have been loaded for this document."
Could this have something to do with the fact that I am using the method where I have an "ActivityPack" project and I have branched the build script into a directory in this project. I have pointed the team explorer to this branched build script.
Look at your Output window while you are attached to TFSBuildServiceHost.exe. Do you have a line like this
Instrumentation for debugger fails. Reason: Could not find file 'c:\blah\blah\blah\BuildProcessTemplates\MyBuildTemplate.xaml'..'TFSBuildServiceHost.exe' (Managed (v4.0.30319)): Loaded 'Workflow'
The build template file records the path to itself inside the file. Open up your build process template file in a text editor. Look for a XamlDebuggerXmlReader.FileName attribute within. If the value of that attribute doesn't match the actual file location of the xaml file you had open when you were setting breakpoints, the debugger will not be able to hit those breakpoints.
I've built a simple application in Flex Builder 3 with some trace() calls. It's an "ActionScript Project", no MXML or AIR involved. I don't run the app from within Eclipse, I just open the generated html file with Firefox.
I'm using the Flash Player 10 Debug version. I've correctly set mm.cnf to log trace output, following the official instructions. A flashlog.txt file is generate in the appropriate location.
Despite all that, trace output is not shown in the log file. What am I doing wrong?
(I suspect it's a compiler option, but I can find no such option in the project options in FlexBuilder)
(If I do run the app from Eclipse, by pressing F11, I can see trace output but only inside Eclipse, not in the log file)
Try setting the -debug compiler argument to true.
Is there anything in the flashlog.txt, or is it completely empty?
Perhaps you can use De MonsterDebugger instead?
De MonsterDebugger is an open source debugger for Adobe Flash, Flex and AIR. De MonsterDebugger is made in Flex and AIR by design studio De Monsters.
If that doesn't work google "fxspy" or "Alcon debugger". Those are two other good debugging options.
Somehow it solved itself