As I've been debugging this issue: http://xrdp-devel.766250.n3.nabble.com/XRDP-performance-under-heavy-packet-loss-10-20-td4025265.html
I've noticed that most components in XRDP are compiled with -O2. This means "heavily optimized" which makes debugging the xrdp module difficult as many of the variables are optimized out. When I attempt to change line 3493 on /xrdp.git/configure: From: CFLAGS = "-g -O2" To: CFLAGS = "-g -Og" And then re-run automake (./configure --enable-jpeg --enable-xrdpdebug), I get the following error: ./configure: line 11471: --variable=systemdsystemunitdir: command not found checking for openssl/rc4.h... no configure: error: please install libssl-dev or openssl-devel ...Yet, libssl-dev, and a whole bunch of other libssl* variants are installed, same is true with openssl, and it STILL gives me this error. What is the problem here? Is it not possible to build a truly debug-optimized build of XRDP? What does --enable-xrdpdebug actually do, then? It doesn't seem to enable the DEBUG compiler option in sesman (which is what I need at the moment) -- View this message in context: http://xrdp-devel.766250.n3.nabble.com/Enabling-debug-builds-for-XRDP-tp4025289.html Sent from the XRDP Devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
