I Had a Qt program which was working fine in Linux . We migrated our linux from 32bit to 64 bit and while trying to run the same program again throws me a error given below
"During Startup program exited with code 127"
In the Output window I also see the following:
&"warning: GDB: Failed to set controlling terminal: Invalid
argument\n" &"Cannor exec /bin/tcsh: No such file or directory.\n"
does anyone have any idea on this error??
A Thread in QtCentre has the same problem solved.
Look at here
Hope that helps...
Related
I'm debugging qmake in Qt Creator using Debug/Start Debugging/Start and Debug External Application... . It can break at the main function. I can step into the runQMake function. Then when I pressed F10 to step to the next line, gdb terminated. The messages in the debug log window when GDB terminated are:
Step next requested...
<36-exec-next
dHANDLE GDB ERROR: The process was ended forcefully.
dProcess crashed
dGDB PROCESS FINISHED, status 1, exit code -1073741819
dNOTE: INFERIOR ILL
dState changed from InferiorRunRequested(7) to InferiorRunFailed(9)
dState changed from InferiorRunFailed(9) to InferiorStopOk(11)
dState changed from InferiorStopOk(11) to InferiorShutdownRequested(13)
dCALL: SHUTDOWN INFERIOR
dRUNNING NEEDS-STOP COMMAND kill
dUNSAFE STATE FOR QUEUED COMMAND. EXECUTING IMMEDIATELY
<37kill
My compiler is Mingw, gdb version 8.1, Qt creator 5.12. Can anybody shed light on this problem? What could cause this problem? BTW, why cannot I see the first character("d") of every line of the log messages in the debug log window but the character is there when I copy and paste the messages here? Thanks!
I am trying to compile Nginx with Visual Studio 2015, as a project. I followed this tutorial : Compile NGINX with Visual Studio , which worked pretty well (even if it was made for VS 2010).
I was finally able to launch nginx.exe but the webserver doesn't work yet, several things :
Release mode
The program exits with the messages :
The thread 0x25ac has exited with code 2 (0x2).
The thread 0xe64 has exited with code 2 (0x2).
The thread 0x1a60 has exited with code 2 (0x2).
The program '[13872] nginx.exe' has exited with code 2 (0x2).
The error.log file contains :
2018/05/28 15:26:09 [crit] 13872#4024: CreateProcess("my\nginx\path\Nginx\Release\nginx.exe") failed (5: FormatMessage() error:(15100))
Debug Mode
The program exits with the messages :
The thread 0x18a8 has exited with code 1 (0x1).
The thread 0x3064 has exited with code 1 (0x1).
The thread 0x2bbc has exited with code 1 (0x1).
The program '[6868] Nginx.exe' has exited with code 1 (0x1).
The error.log file contains :
2018/05/28 14:14:25 [emerg] 13152#14248: CreateDirectory() "my/nginx/path/Nginx/Debug/temp/client_body_temp" failed (123: FormatMessage() error:(15100))
Here's the arborescence of my/nginx/path/Nginx/Debug/ and my/nginx/path/Nginx/Release/ :
nginx.exe
conf/
nginx.conf
a bunch of other conf files
html/
index.html
logs/
error.log
acces.log
nginx.pid
temp/
client_body_temp/
Note : I myself created the different files and folder, the program was unable to do it.
nginx.conf
Last, I'm unable to modify the path of my error.log in nginx.conf. When I try to do it, it seems to have no effect at all.The command
error_log logs/error_bis.log;
does not create error_bis.log or does not write in it if I create the file.
Note : the prefix path is set when I launch nginx.exe with the command argument
-p my/nginx/path/Nginx/Debug
And last thing, I have the admin privileges.
I finally solved my problem.
CreateDirectory was calling CreateDirectoryW instead of CreateDirectoryA beacause UNICODE was defined. An unsigned char* was given to the function instead of a LPWSTR.
I just had to set "Character Set" (in Property->General->Project Defaults) from "Unicode" to "No set". Everything works now.
I just built standard core 15.09a on linux and run sample apps basic_client.
This one built by scons.
bin/samples/basic_client works fine.
However, I built cpp/samples/basic/basic_client with Makefile.
It does not work. It shows an error
"0.232 ****** ERROR ALLJOYN external ...e/src/BusAttachment.cc:560 | BusAttachment::Connect failed: ER_OS_ERROR
BusAttachment::Connect('') failed.".
So, I launched the bin/allhoyn-daemon, then no error occurred.
What is difference between scon and Makefile version?
Additionally, where can I get the information of application under the bin directory?
I searched the web-site of AllSeen and couldn't find any info.
As i know, the error that you got when build with Makefile happens because basic_client hasn't alljoyn router inside, with scons it runs fine because it compiles with BR=on and some flags:
-lajrouter -lBundledRouter.o -lssl -lcrypto
For more infomation, visit: here
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.
I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.