>> It may be easier just for you to start guacd directly with gdb and get the >> information that way. Basically, you'll need to: >> * Make sure gdb is installed, using your package manager for whatever >> distribution you're running. >> * Launch guacd via gdb, as follows: gdb --args /path/to/guacd -L debug -f >> * You'll get a gdb> prompt, and you can type "run" >> * Attempt the connection, reproducing the segmentation fault. >> * Once the segfault occurs, gdb will drop to the gdb> prompt, again, and you >> can then type "bt full" to get the full backtrace. >> * Make sure to remove any sensitive data - for example, when I was debugging >> a segfault with 1.5.2, it would print out my connection parameters, >> including username/password for the server I was logging into.
If I am allowed to do so, how do I run the gdb command without affecting production users using the web application? According to https://access.redhat.com/documentation/es-es/red_hat_enterprise_linux/7/html/developer_guide/debugging-running-application Would I run gdb using: "Attach GDB to an already running process", which is in 20.2.2 section as I have indicated? Once I'm at the gdb prompt, what should I run? bt full? -Gabriel
