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

2020-02-10 Thread Mike Jumper (Jira)


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

Mike Jumper commented on GUACAMOLE-950:
---

Yes, thanks, this is perfect.

> 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 Creek
>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)


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

2020-02-10 Thread Toby (Jira)


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

Toby commented on GUACAMOLE-950:


Am I getting closer to the data that will help?

#0 0x in ()
#1 0x7fa2deb05f09 in fastpath_recv_update 
(fastpath=fastpath@entry=0x7fa2cc02b190, updateCode=, 
size=size@entry=4, s=s@entry=0x7fa2cc025050) at ./libfreerdp/core/fastpath.c:438
#2 0x7fa2deb06a12 in fastpath_recv_update_data (s=0x7fa2cc025050, 
fastpath=0x7fa2cc02b190) at ./libfreerdp/core/fastpath.c:538
#3 0x7fa2deb06a12 in fastpath_recv_updates (fastpath=0x7fa2cc02b190, 
s=s@entry=0x7fa2cc025050) at ./libfreerdp/core/fastpath.c:666
#4 0x7fa2deb014b6 in rdp_recv_fastpath_pdu (s=0x7fa2cc025050, 
rdp=0x7fa2cc016b00) at ./libfreerdp/core/rdp.c:1292
#5 0x7fa2deb014b6 in rdp_recv_pdu (rdp=rdp@entry=0x7fa2cc016b00, 
s=s@entry=0x7fa2cc025050) at ./libfreerdp/core/rdp.c:1300
#6 0x7fa2deb02113 in rdp_recv_callback (transport=, 
s=0x7fa2cc025050, extra=0x7fa2cc016b00)
 at ./libfreerdp/core/rdp.c:1446
#7 0x7fa2deb0a229 in transport_check_fds 
(transport=transport@entry=0x7fa2cc024b30) at ./libfreerdp/core/transport.c:1030
#8 0x7fa2deb025f8 in rdp_check_fds (rdp=0x7fa2cc016b00) at 
./libfreerdp/core/rdp.c:1505
#9 0x7fa2deaed667 in freerdp_check_fds (instance=0x7fa2cc00bb20) at 
./libfreerdp/core/freerdp.c:316
#10 0x7fa2deaee451 in freerdp_check_event_handles (context=0x7fa2cc011a30) 
at ./libfreerdp/core/freerdp.c:365
#11 0x7fa2dede5bba in guac_rdp_handle_connection (client=0x7fa2d800b350) at 
rdp.c:428
#12 0x7fa2dede60df in guac_rdp_client_thread (data=0x7fa2d800b350) at 
rdp.c:641
#13 0x7fa2e38f86db in start_thread (arg=0x7fa2d280f700) at 
pthread_create.c:463
#14 0x7fa2e339488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

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


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

2020-02-10 Thread Mike Jumper (Jira)


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

Mike Jumper commented on GUACAMOLE-950:
---

Does your distribution provide a package containing the debug symbols for 
libfreerdp? That should allow gdb to produce a backtrace that includes line 
numbers, filenames, etc., for the FreeRDP portion of the stack. Since stack 
frame #0 shows the instruction pointer as all zeroes, it looks like there must 
be some function pointer FreeRDP is expecting to be assigned but is {{NULL}} in 
our case.

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


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

2020-02-09 Thread Toby (Jira)


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

Toby commented on GUACAMOLE-950:


I could not run gdb against guacd live as I got timeouts on connect.

I set ulimit to dump cores, and ran the gdb against the core.  Output below:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/sbin/guacd -p /var/run/guacd.pid'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x in ?? ()
[Current thread is 1 (Thread 0x7fdc6f0dc700 (LWP 24601))]
(gdb) bt
#0 0x in ()
#1 0x7fdc7b4f8f09 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#2 0x7fdc7b4f9a12 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#3 0x7fdc7b4f44b6 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#4 0x7fdc7b4f5113 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#5 0x7fdc7b4fd229 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#6 0x7fdc7b4f55f8 in () at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#7 0x7fdc7b4e0667 in freerdp_check_fds ()
 at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#8 0x7fdc7b4e1451 in freerdp_check_event_handles ()
 at /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
#9 0x7fdc7b7d1757 in guac_rdp_handle_connection (client=0x7fdc7400b350)
 at rdp.c:428
#10 0x7fdc7b7d1757 in guac_rdp_client_thread (data=0x7fdc7400b350)
 at rdp.c:641
#11 0x7fdc800726db in start_thread (arg=0x7fdc6f0dc700)
 at pthread_create.c:463
#12 0x7fdc7fb0e88f in clone ()
 at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

 

What else can I provide?

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


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

2020-02-07 Thread Nick Couchman (Jira)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)