I am new to Bazel and running my first build command bazel build //path-to-code however it logs/prints nothing on the terminal. I tried verbose, explain etc options but none of them worked.
Can someone help me debug this? Any pointer to exiting similar posts would also be helpful.
Related
have some real trouble with QtCreator on ubuntu 18 and was wondering if anyone could give me any help. This morning I installed cmake for another project I was working on, now when I try to run a project in qtcreator it is trying to deploy it via FTP, even though it is a Qt c++ project. I dont know if this is anything to do with cmake, but this worked last night before I installed it. My question is, can anybody explain to me how to run a project from QtCreator, on the local system( Terminal or otherwise, doesnt matter ) without any deployment issues. Im sorry if this is a stupid question, but I am extremely grateful for any hep
In a console, you can just cd into the project directory (where the .pro file resides) and execute "qmake" and then "make". That should compile your executable which you can then run using "./[executable filename]" or "/[path]/[executable filename]". Also, on the console you might see where this FTP transfer comes from. Also, in QtCreator you can set the build system and change that from cmake to something else to see if its a cmake problem.
So, not sure how this issue came up, but I have found a workaround after much trial and error. Open a project, In the left tab click Projects and under build and run select Run. In this menu deploy steps have already been added when i create a project, so these need to be deleted. Now in the Run section on the same screen Click add -> Custom executable and select the file that has already been built for the project in question. In my case this solves the above problem, but does not explain why QtCreator is trying to deploy C++ projects via FTP. If anyone out there is struggling with this issue feel free to post a question here and I will assist as much as possible!
I have OSX Yosemite 10.10.5, QtCreator 4.1.0, Qt 5.7.0 and Xcode 7.2.1.
If I write any native C++ program in QtCreator (console, gui - anything) I am unable to debug that program from QtCreator. Breakpoints get ignored, the program executes without pause and runs to completion no matter what I try.
I have tried the Xcode's LLDb, system GDB and Homebrew GDB as debuggers. the versions of GDB fail to start. Homebrew GDB has been codesigned.
This all used to (a few year back) just work beautifully and I am at a loss as to what might have changed.
Curiously, if I generate an exception inside the program - like accessing through a null pointer, the debugger shows me where this happens in just the way I would expect so, presumably, the debugger is running but simply treating me with complete disdain.
I know there are many versions of this question but none seem to address the problem adequately or offer workable solutions, or they apply to much older versions of the products.
Any suggestions?
This version of qtCreator (4.1.0) saw the return of the warning about having the build directory at the same level as the project directory. In Windows, this is done automatically. My mac installation does not get it right. (I may have messed a while back - cannot remember).
So - if the build directory is inside the project directory, debugging fails. Move the build directory up to the same level as the project directory and everything seems to work fine.
You can set the default build directory in the preferences/Build & Run dialogue. The path should start with ../
You will need to think about the folder structure before setting up the project unless you want build folders appearing in awkward places. So, a project folder structure like this is OK:
But one like this is not:
If this was already obvious to you, great. I have been messing with this for ages.
Many thanks to those who replied and anyone else who took the time to read the question. What helped e find it was the suggestion by #AlexanderVX that his setup was the same as mine but his worked. The only bit of my setup he could not see in the screenshots was the start of the build path. So that was the clue.
I have built openJDK the debugging version with the following configuration options in README-builds
bash ./configure ---with-debug-level=slowdebug --with-target-bits=64
However I cannot set any breakpoints or to be correct there are no symbols, doing some reseach on google I have found out that I should extract .diz (libjvm.diz) files in lib folder, but this does not seem to work.
I will answer this for other people, after you get the sources
Follow the steps:
bash ./configure --with-debug-level=slowdebug --with-target-bits=64 --disable-zip-debug-info
make all
An information worth mentioning that finally when you start the debugging session with gdb and you run the program you may see a SEGFAULT ignore it and continue till gdb stops at your breakpoint.
When i want to run a program with arguments out of the IDE i do this:
ProjectProperties→Run→Arguments and type my arguments in there.
But if I want to Debug, NetBeans ignores these arguments given there.
So how can I debug a project with command-line-arguments given?
I had the same issue.. My NetBeans C project don't take command line arguments in debug mode.., but only with run (F6)..
..
What I've done (NetBeans/MinGW):
uninstall mingw-get
run mingw-get-inst-20100909.exe (this has gdb 7.1).
http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20100909/
This is a temporarry solution until binary NetBeans 6.9.2 release will be available..
Hope this help someone..
I had the same issue with Netbeans 6.9 but not 6.8, and found that the solution was to update Netbeans.
http://forums.netbeans.org/topic36082.html
I have the same issue, and there is a way to get around it.
First, you need to enable GDB console within NetBeans, by setting this options on your netbeans config file (you will have to close NetBeans for it to work)
-J-Dgdb.console.window=true
Next, on NetBeans and before you start your program, set a break point right at the start of your main(). Once execution breaks there, use the "set args [arguments]" gdb command followed by "run" to restart your debugged program, now with the arguments set.
You do not need to close the debug session when you rebuild your project, as GDB will detect it and reload the new binary when you issue the "run" command again; this way you wont have to set the arguments again.
So, I'm starting a C++ class right now, and I've configured NetBeans (which I use normally for PHP and Java Development) to use the Cygwin compiler/debugger. This is my first structured experience with C++, and I'm running into a slight issue. When I attempt to run a program within NetBeans (F11 or the Green Triangle) the project builds correctly, no errors or warnings, but then won't run. I receive the following error:
The application failed with exit code -1073741515 (0xc0000135).
This could indicate that no required .dll was found in the PATH.
Please try to start the following command from the command shell (cmd.exe).
This may give some additional information.
C:/Users/Eric/Documents/NetBeansProjects/CS217ASeminar1/dist/Debug/Cygwin-Windows/cs217aseminar1
RUN FAILED (exit value -1,073,741,515, total time: 58ms)
When I attempt to execute the given file within a command shell, I get no errors and the program runs successfully. The research I've done on this error usually indicates that C:\cygwin and/or C:\cygwin\bin (my install directories) aren't in the path. However, I've verified that I they've been added to the path, and I can run arbitrary programs from both of those folders.
Does anyone have any suggestions on how to resolve this error, or any experience with something similar? Obviously, it's not a huge deal, but I'd like to be able to use NetBeans's built in functionality.
Thanks in advance.
Edit: After tinkering a bit with the settings of my project in an attempt to fix it, it appears that the error was being caused by the Profiler in NetBeans. Since that only works on Linux/Solaris, and this is a Windows 7 box, disabling that caused no loss of functionality and solved the issue. Thanks for everyone who tried to help.
After tinkering a bit with the settings of my project in an attempt to fix it, it appears that the error was being caused by the Profiler in NetBeans. Since that only works on Linux/Solaris, and this is a Windows 7 box, disabling that caused no loss of functionality and solved the issue. Thanks for everyone who tried to help.
Right click on project change set configuration from debug to release. It worked for me.
Might be wrong, but it sounds like your path might not be set correctly...
Netbeans docs