From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 60182] X.Org Server terminate when I close video player Date: Wed, 11 Sep 2013 03:29:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1538896044==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0FDFFE601A for ; Tue, 10 Sep 2013 20:29:56 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1538896044== Content-Type: multipart/alternative; boundary="1378870196.c7bac6B0.8712"; charset="us-ascii" --1378870196.c7bac6B0.8712 Date: Wed, 11 Sep 2013 03:29:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=60182 --- Comment #26 from Weber K. --- During a test, I needed to issue 2 "cont" commands at gdb to advance just one frame at one breakpoint I trapped. And when closing the player, I issued twice "cont" at gdb, and only after the segfault occured. I suspect the function "radeon_dri2_screen_init" at "radeon_dri2.c" is called twice, one for each Screen, and then this routine is scheduling the "radeon_dri2_client_state_changed" routine twice with "AddCallBack". This way, when the client state is changed to gone, the "destroy buffers" routine is called twice either, and the error occur. I also want to thank the devs for the radeon driver! Thank you! -- You are receiving this mail because: You are the assignee for the bug. --1378870196.c7bac6B0.8712 Date: Wed, 11 Sep 2013 03:29:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 26 on bug 60182 from 
During a test, I needed to issue 2 "cont" commands at gdb to advance just one
frame at one breakpoint I trapped. And when closing the player, I issued twice
"cont" at gdb, and only after the segfault occured.

I suspect the function "radeon_dri2_screen_init" at "radeon_dri2.c" is called
twice, one for each Screen, and then this routine is scheduling the
"radeon_dri2_client_state_changed" routine twice with "AddCallBack".

This way, when the client state is changed to gone, the "destroy buffers"
routine is called twice either, and the error occur.

I also want to thank the devs for the radeon driver!
Thank you!

You are receiving this mail because:
  • You are the assignee for the bug.
--1378870196.c7bac6B0.8712-- --===============1538896044== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1538896044==--