I have installed graphviz-2.38, and I have included the dmtracedump path inorder to execute from command line. I am trying to view call graph of the .trace file stored in my system. I executed the below command, but it seems to be not working as no output files have been generated. Please help in resolving the error.
C:\Users\rb>dmtracedump -ho -s D:\Android\logs\cpu-art-single-call.trace -g D:\Android\logs\be cpu-art-single-call.trace
C:\Users\rb>
Related
I'm trying to init my first NestJS project but met this fail:
-----------------------------------------
$ nest new testproj
⚡ We will scaffold your app in a few seconds..
'node' is not recognized as an internal or external command,
operable program or batch file.
Failed to execute command: node #nestjs/schematics:application --name=testproj --directory=undefined --no-dry-run --no-skip-git --no-strict --package-manager=undefined --language="ts" --collection="#nestjs/schematics"
------------------------------------------
Tryed to reinstall NodeJS, but no luck.
$ node -v
v16.13.1
$ nest -v
8.1.6
$ npm -v
8.3.0
Any help will be appreciated.
tl;dr:
If your PATH somewhere has a file in it and not a folder (can also be in the middle of a path, with some \other\stuff appended like C:\stuff\somefile.txt\stuff), then this can happen due to an error when Git bash is translating PATH before calling cmd.exe, resulting in part of the PATH not being forwarded and making binaries in that part "not found".
Details:
After some investigation via chat, it turned out that the root cause was a bad GRADLE_HOME environment variable.
Yes, Gradle has nothing to do with node.js or nest, but bear with me, this is one of those moments where a TV episode starts with a totally crazy scene and you wonder what the heck happened that led to this, and then you get "6 hours earlier..." 😁
So, Git bash obviously succeeded in finding node, because it ran the nest CLI (which is a node script). But then, somehow, cmd (which is called by node when executing shell commands) did not find node. This normally should not happen.
Tracing the events with Process Monitor revealed that bash (sh.exe) passed a truncated PATH variable to node.exe. It just ended abruptly somewhere in the middle, and C:\Program Files\nodejs (which was towards the end of it) was not passed along.
The reason for this turned out to be an entry in the PATH that looked like this: C:\foobar\file.zip\bin. The transition into bash worked, as the full path (including this bad entry as /c/foobar/file.zip/bin) could be seen in bash's $PATH, and /c/Program Files/nodejs was there too.
But the transition from bash to node.exe failed. In the process of converting the Linux-style paths to Windows-style paths before passing the variable on to node.exe, bash silently failed in the middle of the string and stopped processing it - as soon as this /c/foobar/file.zip/bin entry was encountered. C:\foobar\file.zip did exist, and it turns out Git bash behaves like this when it unexpectedly encounters a "not a directory" error from the OS when querying the path segment ("file not found" is fine) - as a result of attempting to access a "subdirectory" of a file. Removing this entry from the PATH made everything work normally.
The source of this entry was actually %GRADLE_PATH%\bin in the Windows PATH, and the reason this caused the problem was that GRADLE_PATH itself was incorrectly set to a file (C:\foobar\file.zip) instead of a directory.
There are three ways to resolve this:
Remove %GRADLE_PATH%\bin from the PATH.
Fix GRADLE_PATH to point to a directory.
Delete or rename the C:\foobar\file.zip file.
Using a very helpful thread here and these steps, I added make to my path (as C:\Program Files (x86)\GnuWin32\bin\make.exe).When I call $Path this shows up. However when I try to run make S4_pyext in cmd.exe which I run from Anaconda3, I get an error
'make' is not recognized as an internal or external command, operable program or batch file.
I thought I may have not added make to the path correctly so ran
"C:\Program Files (x86)\GnuWin32\bin\make.exe" S4_pyext
Instead which resulted in an error
mkdir -p build A subdirectory or file -p already exists. Error occurred while processing: -p. A subdirectory or file build already exists. Error occurred while processing: build. make: *** [objdir] Error 1
I can't seem to make heads or tails of this error message. Does anyone know what may be happening on either attempt?
I am attempting to use pylint's pyreverse to generate uml diagrams of some .
When I run pyreverse from the command shell
pyreverse <modulename>
It executes just fine and returns a *.dot file as it should. If I attempt to use output options such as "-o png" I get the following error
>pyreverse -o png <modulename>
'c:\Program' is not recognized as an internal or external command,
operable program or batch file.
I am running python 3.6.5 and pylint 2.1.1.
I have installed graphviz 2.38 under C:\Programs and added the bin directory to my windows path.
I suspect pyreverse is recognizing some command as a command and a set of arguments (e.g. "C:\Program Files\blah blah" is being sent as a command to the windows interpreter as "C:\Program", but I do not know where, or how to fix it.
Can anyone offer any solutions?
That is a bug as the commenter suggested.
In the meanwhile, install graphviz, so that dot is on the path, then run
dot -Tpng classes.dot>result.png
I have the binary file to install a component when i am running using ./filename.bin it comes into console mode and asks for language selection and directory selection and all , i tried ./filename.bin -r path/response.properties, help me if anyone knows.
as you said that you have already tried using ./filename.bin -r path/response.properties and still it does not work then , do one thing go for the console mode while creating the response file like :-
./filename.bin -i console -r path/response.properties
then install what you are installing, the response file will capture that.
And to use that later you can just include tat while running your bin file to take the input from response file.
I am a newbie to Linux and I am only really using it to use a program for my final year thesis. I have got to grips with the language for the program but am having issues with actually running it in Linux. The program is called "CACTUS" and all documentation can be found here.
I have extracted the application file and I have made the executable as instructed in the install.txt file:
"Installation of CACTUS for Linux or Mac machines.
Unzip the directory and put in desired location. On terminal cd into the
correct directory (you should be able to see the makefiles).
Create the executable by typing:
$make
or
$make -f Makefile.gfortran
on the terminal. The executable will be called cactus and be located in the
directory one level above.You can add the executable's location to your path
so that you can call it by simple typing cactus on the terminal instead of
the complete path.
cd into the Test/RegTest directory
$cd ./Test/RegTest
and run the RegTest by executing runreg.py with the path to the CACTUS
executable as an argument (or just the name of the executable if you added it
to your path).
$./runreg.py ../../../cactus
or
$./runreg.py cactus
The output should say 'No differences' for all three tests. Note: if you have
Python 3 installed used runreg_p3.py instead.
CONGRATULATIONS! You have successfully installed CACTUS.
I have run this and I didn't get the "No Differences" returned on the runreg.py. I continued anyway as I did not know why or how I could fix this. (This may be a root cause of my overally problem here)
As I progressed I have been trying to open an input file "TestVAWT.in" from TestCase2 with the following command:
./TestVAWT.in ../../../cactus
From this I get the error in the title returned. Am I correct in assuming that it has tried to run the TestVAWT.in file on the command line without referring to the Cactus application which I presume would be able to read the '&' prefix of the code along with the rest of the input file. Or is it something else I am missing here.
I would appreciate any help as I have been banging my head against a wall for some time now.
Note: I am using Ubuntu 14.04 LTS.
Best Regards
Richard
Don't know the application, but looks kind of strange to me.
Please try adding the Input-File as a parameter:
cactus TestVAWT.in