I just built the latest SVN copy of X11rdp (r295) because I wanted to get
the new RanR stuff. When building after running, I get a segfault with the
following stack trace:
Program received signal SIGSEGV, Segmentation fault.
0x00000033e147ae0f in memset () from /lib64/libc.so.6
(gdb) bt
#0 0x00000033e147ae0f in memset () from /lib64/libc.so.6
#1 0x00000000004a97fd in g_malloc ()
#2 0x00000000004a39d8 in rdpScreenInit ()
#3 0x000000000041e4b2 in AddScreen (pfnInit=0x4a3470 <rdpScreenInit>,
argc=2,
argv=0x7fff9ca0f218) at main.c:775
#4 0x00000000004a3434 in InitOutput ()
#5 0x000000000041ecbf in main (argc=2, argv=0x7fff9ca0f218,
envp=0x7fff9ca0f230) at main.c:372
Before crashing, the output is:
(gdb) run
Starting program:
/home/ostler/xrdp/x11rdp_xorg71/xorg-server-X11R7.1-1.1.0/hw/rdp/X11rdp :1
X11rdp, an X server for xrdp
Version 0.5.0
Copyright (C) 2005-2008 Jay Sorg
See http://xrdp.sf.net for information on xrdp.
Underlying X server release 70100000, The X.Org Foundation
Xorg Release 7.1
Screen width 800 height 600 depth 8 bpp 8
dpix 100 dpiy 100
buffer size 480000
The line this seems to be coming from is rdpmain.c:211:
g_rdpScreen.pfbMemory = (char*)g_malloc(2048 * 2048 * 4, 1);
Since the fault is coming up in memset, it seems that g_malloc must be
passing in a bad pointer. However, the implementation in rdpmisc.c looks
sane.
Has anyone else come across this, or have any ideas for tracking it down?
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
xrdp-devel mailing list
xrdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xrdp-devel
