I just wrote a script that calls a project I got from github that calls a normal telephone number and during development I ran the script without a problem. But deploying it on my server and testing it there I get the following error message
Starting sipcmd
in debug mode
Manager
Init
initialising SIP endpoint...
TestChanAudio
TestChanAudio
Listening for SIP signalling on 0.0.0.0:5060
assert.cxx(112) PWLib Assertion fail: Function pthread_setschedparam failed, file ptlib/unix/tlibthrd.cxx, line 745, Error=1
Assertion fail: Function pthread_setschedparam failed, file ptlib/unix/tlibthrd.cxx, line 745, Error=1
<A>bort, <C>ore dump, <T>hrow exception, <I>gnore?
Both machines are running linux and every single library is perfectly installed.
Does someone know how to fix this?
The error code is EPERM so according to the documentation the user running your application doesn't have permission to set the specified policy.
The policy only allows setting the scheduler priority so I guess the application is asking for a priority higher than the user is allowed to use? This question may hold some clues on how to fix this: Why does pthread_setschedparam() produce EPERM on opensuse 11.4
Related
In C++Builder 10.3.3, when running my application, it stops the process and pops up with an error:
Unable to create process: Access denied
I don't know why this happens, and for the life of me I can't figure out what it is talking about.
I tried to build the solution to see if the error was occurring there, and it appears this is the case. After building the solution, the compiler stops the process and a fatal error pops up:
[ilink32 Error] Fatal: Could not open.\Win32\Debug\TabbedApplication.exe (program still running?)
Does anyone know what this error means, and how to fix it?
I added a new target platform in my project in the right
I added windows 64 bit and it worked
hope it helps
I've been getting this messages for months (even with previous verions of RAD studio) and i haven't found a solution yet.
I have used a process explorer and the process is not running but if i close and reopen the IDE the file is not locked anymore.
So i think the problem it's related with the "debugger" that stills is locking the file even when the IDE stopped the debugging process.
I have tried even the "unlocker" utility but it doesn't detect any process is locking the file ...
For know we have to wait until the debugger release the file.
These is the configuration i have tried in the registry:
HKCU\Software\Embarcadero\BDS\20.0\Debugging\Embarcadero Debuggers\Evaluators
[dedfault] REG_SZ dcc32260.dll
com32x.dll REG_SZ -1
dcc32260.dll REG_SZ 0
According to Microsoft, "If [the system] cannot locate the DLL, the system terminates the process and displays a dialog box that reports the error. " This is the result I get when I run my application outside of the command line, but I do not get the same system error when I run the application from a shell environment such as command prompt or powershell.
Is there a way to show the same error message when the application is run from a command line interface?
https://msdn.microsoft.com/en-us/library/aa271571(v=vs.60).aspx
SetErrorMode(GetErrorMode() & ~SEM_FAILCRITICALERRORS);
but I don't think you want to do this, as you do not know in which environment the user will run your application.
It is usually now a good idea to popup a dialogbox in e.g. a service environment.
What is the problem with examining the error code of whatever is failing e.g. LoadLibrary() and reacting to this error?
Using debug I can run my project only one time. After that every time I get error:
cannot open output file debug\trud1.exe: Permission denied error:
ld returned 1 exit status
I close running Qt projects but seems like I can not close this one even via task manager (theres no tasks trud1.exe).
Explorer does not let me delete trud1.exe because it is used by my "System" (i can not kill this process).
Restarting Qt does not help me, only restarting computer does.
Please help me solve my problem.
This happens because you have to close the program you've launched before.
Look it isn't running on background.
I'm having a problem debugging a command line program on OS X. I've used this same source file with the same g++ command line hundreds of times to test things with the Crypto++ library.
Under GDB, I get the following after loading the EXE:
$ gdb ./cryptopp-test.exe
...
(gdb) r
Starting program: /Users/jwalton/cryptopp-test.exe
Unable to find Mach task port for process-id 42811: (os/kern) failure (0x5).
Under LLDB, I get the following:
$ lldb ./cryptopp-test.exe
Current executable set to './cryptopp-test.exe' (x86_64).
(lldb) r
error: initial process state wasn't stopped: exited
I've recompiled the program a few times, and I can't get it to run under a debugger. I'm getting a segfault when trying to run outside the debugger too, so that may be a symptom here also.
OS X is 10.8.5, and Xcode is 5.1.1 (5B1008). Everything is fully patched. The only thing to change recently is signing up for a developer account, which is broken thanks to Apple's DRM crap. I can't seem to get any of it to work with Xcode or the command line even though Roots and Certificates are in my Keychain. But this program does not use code signing.
What is causing the initial process state wasn't stopped: exited error, and how do I fix it?
The errors that you have received are usually a direct correlation of a codesigning issue, not with your executable, but with gdb and lldb themselves.
You have a couple of options:
Launch gdb or lldb as sudo (which ignores the codesign req to run executables)
Create a codesigning certificate for gdb or lldb in Keychain.app
Obviously the first option is quickest, but probably should be avoided as it opens up the possibility of bad things happening with elevated permissions.
With option #2 you can likely get gdb or lldb properly working by doing this:
Launch /Applications/Utilities/Keychain Access.app
Select the Keychain Access -> Certificate Assistant -> Create a Certificate...
Choose a name for the new certificate (for example lldb-cert or gdb-cert)
Set Identity Type to Self Signed Root
Set Certificate Type to Code Signing
Select the Let me override defaults option
Continue until the "Specify a Location For The Certificate" screen appears
Set Keychain to System and Continue
In the view showing your certificates, double-click on the one just created and then set "When using this certificate" to "Always Trust"
In Terminal:
codesign -f -s "gdb-cert" /path/to/gdb (or) "lldb-cert" /path/to/lldb
You might have to restart for this to effectively take hold.
There are more concise instructions here for gdb and here for lldb on the codesigning process.
Qt creator throws an error every time I want to start debugging. Here is the error:
ptrace: Operation not permitted.
Could not attach to the process. Make sure no other debugger traces this process.
Check the settings of
/proc/sys/kernel/yama/ptrace_scope
For more details, see /etc/sysctl.d/10-ptrace.conf
I have googled the error message and got some result about bug in the kernel but I am able to run gdb in command line, so I don't think it is kernel/gdb related.
What can be the cause of this error?
I just did some research and found the solution somewhere. It turns out that /proc/sys/kernel/yama/ptrace_scope was set to 1. After I changed it to 0, the problem disappeared.
Explanations of ptrace can be found here and here, as Merlin069 said.