https://bugs.freedesktop.org/show_bug.cgi?id=101998
--- Comment #36 from Michel Dänzer <mic...@daenzer.net> ---
(In reply to Meik Neubauer from comment #35)
> [...] from what I can get out of gdb is that the call stack is pretty clear
> [...]
Right, which is why I'm saying we don't need more backtraces right now.
> The question is, which routine is responsible for setting up the structure in
> ent->slave_dst->drawable.pScreen and why is that not done correctly.
As I said in comment 15, the question is how ppriv->notify_on_damage ends up
being TRUE in ms_dirty_update. The only way I can see that being the case is if
msRequestSharedPixmapNotifyDamage was called before, but xf86-video-amdgpu
doesn't have any code calling the RequestSharedPixmapNotifyDamage hook.
> > We really need answers to the questions in comment 27.
>
> I cannot set up a second machine. Due to network security restrictions here
> I cannot connect between two PCs. And I do not have an external monitor in
> any other location. So running a remote gdb debugging session is out of
> reach.
None of the questions in comment 27 are related to remote access or gdb.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati
