Send the /tmp/NoMachineBacktrace.txt file to the Support Team. Set logging file /tmp/NoMachineBacktrace.txtĥ. If there is a core file, run GDB as root or as sudo user by specifying the binary that generated it: In case of NoMachine, the core file can be generated by:ģ. The first line of its output provides information about the binary, for example:Ĭore was generated by `/usr/NX/bin/ nxserver.bin -daemon Verify if a core file has been generated on the remote machine where you are connecting to and identify which program created it: Install GDB if is it's not already installed: Ģ. Thanks to the the capabilities of the Unix world, NoMachine NX makes it possible to run any graphical application on any operating system across any network connection as if you were sitting in front of your computer. Reproduce the problem and proceed to analyze the core dump with GDB as explained below.ġ. NoMachine NX is a Terminal Server and Remote Access solution based on a comprising set of enterprise class open source technologies. The following instructions should help in most cases, but we recommend to consult the official documentation of your Linux.Įdit the /etc/profile file and change the ulimit line as it follows:Įdit the /etc/nf file and add the following lines to the end of the file: Ensure to turn on the creation of core files. RHEL/CentOS) have it disabled by default. Prerequisite: the system is configured to generate core files. While investigating problems related to a sudden termination of the session, the Support Team could request to run the GDB debugger in the user's environment to examine what happened when the program terminated.
0 kommentar(er)
