[jira] [Commented] (GUACAMOLE-950) segfault in guacd

["Nick Couchman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032781#comment-17032781 ] 

Nick Couchman commented on GUACAMOLE-950:
-----------------------------------------

Yeah, we'll definitely want to see the stack trace.  Basically you either need to start gdb, first, and then run guacd from there, or attach to an existing guacd process.  You'll also want to "set follow-fork-mode child" so that gdb debugs the child guacd process and not the parent guacd process.  After it crashes run "bt" to get the back trace, and send that output.

> segfault in guacd 
> ------------------
>
>                 Key: GUACAMOLE-950
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-950
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-server
>    Affects Versions: 1.1.0
>         Environment: Guacamole 1.1.0 under Tomcat8 on Ubuntu 18.04, running as virtual machine
>            Reporter: Toby
>            Priority: Minor
>         Attachments: trace_connected.txt, trace_segfault.txt
>
>
> Upgraded from 1.0.0 on Ubuntu 16.04 to 1.1.0 on Ubuntu 18.04.  Moved from Tomcat7 to Tomcat8.  Config is largely unchanged.
> Two Windows 10 Enterprise destinations and a third is 2012R2.  One of the two Windows 10 will cause guacd to segfault on connection.  2012R2 works fine.  I see a mouse pointer in the upper left very briefly and then I get home/reconnect/logout.  I have pared the config down to just domain, username, password, NLA security, ignore-cert directives for all three destinations. 
> Uploaded syslog traces, one of a normal connect to the other windows 10 device, one as the segmentation fault I get when connecting to the other.
> Have also tried rebuilding without webp and websockets to no effect.
> I'm happy to build one for gdb and get a core, but I'll need a little help doing that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)