New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking down FreeRDP segfault when working with /gfx and /dynamic-resolution #6888
Comments
@Nexarian ok, these stack traces are
Please add |
For the first and second stack traces, I understand that it seems inconceivable, but I have a very consistent way to reproduce all of these. I'm happy to provide more data. Second, my apologies, I had modified the logging statements to try to figure out what was going on, but there were no logic changes. Here is a stack trace from a clean clone of FreeRDP. The command I used and the /buildconfig are below:
|
So I realized I made a classic blunder. Here's the reset sequence I was sending to FreeRDP:
Can you spot the error? Session width is used twice in create surface instead of matching what was sent from reset_graphics. I don't know if this is a bug you care about. FreeRDP will segfault if reset graphics and create surface are sent different sizes... |
This is from my conversation with @akallabeth earlier. In testing a prototype branch of XRDP, I was able to get FreeRDP to segfault, and I finally got the stack trace:
and another one:
and
The text was updated successfully, but these errors were encountered: