> I'm still trying to track down the re-connection bug that is happening in > XRDP; > > http://xrdp-devel.766250.n3.nabble.com/XRDP-performance-under-heavy-packet-loss-10-20-td4025265.html > > And I want to follow the steps in here: > > http://www.xrdp.org/index.php?option=com_content&view=article&id=20:for-developers-only-x11rdp-chansrv-no-sesman&catid=2:documents&Itemid=7 > > However, the instructions say "this works well for developing any component > in XRDP except sesman." Unfortunately, I'm pretty sure the bug is in sesman, > or at least, debugging sesman is a first step to getting to the bottom of > this issue... So, what is the ideal way to develop for sesman?
Nexarian, Debugging sesman is possible. I can do a document on it. I was looking at the stack trace and it does not look like a sesman issue. What makes you think it's sesman? Sesman pretty much just logs you in and starts process. Jay ------------------------------------------------------------------------------ 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
