I'm using MonoDevelop and MonoTouch to build a project, but whenever there is a compile error in gcc, it simply says (in the Build Output tab), "Process exited with code 1, command: ..."
The problem is, I can't see what error gcc gave. It looks like stderr is either ignored or stuffed into a logfile somewhere.
I thought I might be able to discover the gcc/stderr output if I copy that command to a terminal window and run it, but it won't compile because some of the files on the command line were temp files that MonoTouch setup, and they were removed after MonoDevelop tried to build.
I've tried:
Setting Log Verbosity to Diagnostic
under
MonoDevelop->Preferences->Build
Running mdtool on the command line
with -v and that doesn't show me any
gcc output either
Adding
--stderr=/Users/myname/somefile.txt to the mtouch command line under
Project Options->iPhone Build->Extra
Arguments
.. none of those things work.
So.. how can I get the stderr output from gcc when mtouch runs it?
Add "-v -v -v" to the "Extra Arguments" for your build configuration in the iPhone Build settings.
In the build results window, mouse over the right end of or click on the step causing the error. A small icon will show up at the end of the line. It looks like an oval with horizontal lines going through it. If you click on that, you will see the commands that were run in that build step, as well as the output of those commands.
Related
Please can anyone help me out code runner only shows the right output after running the python file.
For example
Here I used the option "run python file" in terminal and it worked
Then i ran it using coderunner extension and it works
But when i change the output and run it, it doesn't change
It only changes after i run it with python file. So I have to run it in terminal for the right output to show. code runner only mirrors the last output in terminal
This may seem obvious but in the third picture, as you can see from the white circle on the tab where the x to close usually resides indicates that you have not saved the file hence it will output results from the last time you ran it using the 'run python file'. The 'run python file' button saves before running automatically so it would be easy to accidently miss the cause as now its saved with the new input and your code runner will output the new result again making it seem as though its duplicating the 'run python file' button.
I am trying to understand why some of the puppet code do not work as expected. I run the puppet beaker test using "rake beaker" command. I am failing to understand how can I tell netbeans to run this command after I set the break points in the sources. I tried to set the project configuration with the appropriate parameters from following command line which "rake beaker" invokes.
/usr/local/rvm/rubies/ruby-1.9.3-p545/bin/ruby -I
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-support-3.1.0/lib:
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec spec/acceptance --color
But the debugger simply starts and ends?
Any idea, how can I debug a rake task?
Update:
As per this I can start the rake beaker task using the ruby-debug-ide, however it does not break at the break points I have set. As per the blog I believe I have break points set in the files, which will run using ruby-debug-ide.
By the way I am running Netbeans 8.0.1 on CentOS 6.4
One way I found out is to
Create a Netbeans ruby project
Set the breakpoints wherever needed.
Open the rspec binary file in Netbeans editor window.
Debug rspec file, by pressing Ctrl-Shift-F5
Provide the parameters in the debug dialog as shown in picture below
And you are done
I've a very simple Ruby script, which I've used rawr to package up into a *.jar file. I can then run the *.jar file with java -jar *.jar. I would like to make my program into an executable so I did rake rawr:bundle:exe. It says that it successfully created an executable and I can see the executable it created.
What I don't understand is, when I double click the executable (or attempt to run it in the command prompt), it doesn't really do anything; it is supposed to display 'hello' and wait for me to push enter (on STDOUT) but nothing really happens. If I run the *.jar file, it displays 'hello'. How am I supposed to run the executable? I was expecting that when I double click the *.exe, that a command prompt window pop up displaying 'hello' and waiting for me to push enter...
Since the program displays to STDOUT, and doesn't have a GUI component, I think you need to run this from the command prompt. Not sure what OS your on, since you said .exe, I'm assuming windows. so you just need to run it from the command prompt instead of by double-clicking on it.
so in the same folder where you are able to succesfully execute:
java -jar *.jar
just type:
myApplication.exe
Or, if your in another location on the machine you can type:
C:\full\path\to\myApplication.exe
Otherwise, the process is just going to run in the background with no way for you to see the results.
I have a problem when i try to build my makefile project within Eclipse on Linux OS. Whole makefile executes fine except for the last command which is unsimgcr -pd input output. I get an error /bin/bash: unsimgcr: command not found.
The weirdest thing is that if i run make command from linux terminal the makefile executes fine no problems. I think I should set something within Eclipse IDE, but I don't know how and help would be appreciated.
Likely unsimgcr is in your path when you run it from the command line but not in the path when run from eclipse. Either fix the path issues, or put an absolute path to unsimgcr in the make file.
I am using Eclipse along with EPIC plug in and pad walker for running my Perl project.
I am facing a strange issue
If I "Run" the project, the system fails and exits Perl without any error message.
But if I "Debug" the project and then give "Run" the same Perl scripts work fine as expected.
Could anyone let me know the difference in the two mode ("Direct Run" & "Debug & Run")?
Found it in the EPIC source code: EPIC adds the "-d" command line option for the debug target. It does some interesting things with the stdin/stdout too to remotely control the debugger. So maybe there's some side effect there? Can you share the error message?