I just fixed it. It looks like the server sends a pointer cached message for cache index 0 once at connection time, before this index is populated with a pointer, causing the segfault. Since this happens only once at connection time I'm just assuming that the server wants the default system pointer to be used. Adding a check for an invalid pointer cache index and avoiding to notify the UI works.
On Fri, Dec 16, 2011 at 10:14 AM, John Eke <john....@magorcorp.com> wrote: > I've created Issue #281 (https://github.com/FreeRDP/FreeRDP/issues/281) > for thsi bug. > > Thanks Alexis > > On Fri, 2011-12-16 at 11:10 +0100, Alexis Moinet wrote: > > > Alexis Moinet > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Freerdp-devel mailing list > Freerdp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
