Unable to launch rattle - "Memory not mapped" - rstudio

I'm trying to launch rattle on my R console, but whenever I run the rattle command, my R console crashes with a "memory not mapped" error message. Could anyone advise me on what could have gone wrong and how do I resolve this issue?
I am running MacOS Version 10.14.5 and I have installed cairoDevice_2.26.tar.gz and RGtk2_2.20.36.tgz following the instruction posted on this GitHub page (https://gist.github.com/sebkopf/9405675)
error message

Related

How to log the error of an electron windows application : "A javacript error occured in the main process"

I created an electron app. I get this error.
I know that it is due to a native lib not being built against the correct platform. My problem is that the name of the lib doesn't appear in the error message. I tried to run the app in the cmd, but there is no log there. I tried event viewer and I tried to install Process Monitor to detect the errors, but I didn't succeed to find the error log, and I end up with no idea about how to find the complete error message.
I even tried "C:/path/to/my/app.exe" > log.txt 2> errorlog.txt but the 2 files were empty...
Can anyone help me?
Ok. I discovered how to debug a program on Windows... Don't use Windows. I switched to Ubuntu, installed wine, ran the faulty project, and directly got the complete error message. Turns out that the culprit was ref-napi. I solved the original issue this way

Signing error when trying to open executable created with raco (macOS)

I've been breaking my head on this issue and have come to SO to ask for some help. I'm running Racket v7.7 on macOS 10.14. I've built an application with a GUI (https://github.com/layetri/markoviser), and when I compile it with raco exe --gui, all is fine. That is, until I try to execute the created .app. The program seems to start for a few seconds, but then dies. Looking at the Console, tccd gives me the following error:
Failed to copy signing info for 10203, responsible for file:///Users/layetri/Development/markoviser/Markoviser.app/Contents/MacOS/Markoviser: #-67062: Error Domain=NSOSStatusErrorDomain Code=-67062 "(null)"
...after which the program quits. Would anyone know what I'm doing wrong or what I can do about this?

PyCharm quit unexpectedly on MacBook Air

PyCharm closes and sometimes macbook restarts while running my python script on it. The script runs for a while and suddenly I get the following error:
PyCharm quit unexpectedly
Problem details and system configuration:
How to solve this issue please? Thank you
PS: the error message is too long with details so I have just added the initial part which I think should be enough but I can add all of it if required.

AUv3 extension is not registered in MacOS

I am trying to write a small MacOS app with AUV3 extension.
I followed all the instructions, however, the extension is not registered in the system. I suppose to see it in the list when I execute:
pluginkit -mv | grep [MY_EXTENSION_NAME]
command, but I see nothing.
Trying to execute command:
pluginkit -a [MY_EXTENSION_PATH]
does not give any error or any other output at all.
syslog - w
also does not shows any error.
There are no compilation errors or even compilation warnings of any kind.
Maybe someone can direct me to some other error log or some tool or verification that can help me. Is there a place where I can read about the registration process and what can go wrong?
I tried:
Xcode 8.2 on El-Capitan
Xcode 9 Beta on High Sierra Beta

Error running meteor in MAC

I am trying to run meteor app on MAC without success with following error. Surprisingly other project is running properly in MAC and very this project runs properly on Windows. But in MAC I can't figure out what's wrong.
/Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245
throw(ex);
^
Error: Must throw non-empty error
at Object.Future.throw (/Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:259:10)
at /Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/tools/buildmessage.js:541:23
at runWithEnvironment (/Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/tools/fiber-helpers.js:139:21)
at /Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/tools/fiber-helpers.js:146:14
at /Users/user1/.meteor/packages/meteor-tool/.1.1.4.xh5uo++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/tools/buildmessage.js:549:11
The issue is probably related problems fetching the packages, see https://github.com/meteor/meteor/issues/4921

Resources