Chase Douglas wrote: > Roland Scheidegger wrote: >> I'm not sure it has really anything to do with the fence (probably >> could if it's set up wrongly) - maybe it's just the first thing to >> notice that the gpu has locked up. gpu lockups are not easy to debug, >> you need to figure out what was wrong with the commands you sent to >> the gpu. >> >> Roland > > If that's the case, then how can I go about debugging this? I'm not > convinced that I'm performing fencing correctly, but if I am, how can I > find out if I'm sending commands correctly? Without any documentation I > feel a little lost... Not sure, maybe some sort of incremental approach would work best? Maybe try to submit a second commandbuffer which doesn't actually do much.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
