>> 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.

I will try, but it seems this error occurs only in production environment. 
/var/log/messages in development environment does not show error found in 
production environment. I am not allowed to do this kind of operation in that 
environmet.

-Gabriel 

-----Mensaje original-----
De: Nick Couchman <[email protected]> 
Enviado el: miércoles, 7 de junio de 2023 12:13 p. m.
Para: [email protected]
Asunto: Re: guacd error segfault in libguac-client-rdp.so.0.0.0

On Wed, Jun 7, 2023 at 1:44 PM Gabriel Huerta Araujo 
<[email protected]> wrote:
>
> > Usually they're "core.<PID>", so you may want to search for "-name core.\*".
>
>
> I did not find anything:

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.

-Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to