# Stop trace at query fail point? **URL:** \ **Category:** Help!\ **Created:** [May 29, 2019, 5:27pm UTC](https://swi-prolog.discourse.group/t/stop-trace-at-query-fail-point/740 "2019-05-29T17:27:39Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![prodog](https://avatars.discourse-cdn.com/v4/letter/p/57b2e6/32.png) [@prodog](https://swi-prolog.discourse.group/u/prodog)\ **Post date:** [May 29, 2019, 5:27pm UTC](https://swi-prolog.discourse.group/t/stop-trace-at-query-fail-point/740/1 "2019-05-29T17:27:39Z")
I am using SWI-Prolog 8.0.2 on Ubuntu Linux 18.0.4. Is there a way to get the graphical debugger to start tracing at the first place the top level query fails? (i.e. - at the line of code that is final fail that causes the entire query to fail, not intermediate fails). Side note. The graphical debugger has a small cosmetic bug, at least on my Linux version. When it starts up, all the panels are grey without content. All I have to do is resize it a little and everything shows up once it repaints. Nothing major, but I thought I should report it. ---
**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\ **Post date:** [May 29, 2019, 7:55pm UTC](https://swi-prolog.discourse.group/t/stop-trace-at-query-fail-point/740/2 "2019-05-29T19:55:19Z")
It is not easy to tell on which failure this should be trapped. If you can find something, share it. Yip, the repaint problem is know. It has something to do with a resize request that is not answered. It depends on the X11 window manager and I never managed to point it down. A fix is welcome 🙂 ---
**Author:** ![prodog](https://avatars.discourse-cdn.com/v4/letter/p/57b2e6/32.png) [@prodog](https://swi-prolog.discourse.group/u/prodog)\ **Post date:** [May 29, 2019, 8:39pm UTC](https://swi-prolog.discourse.group/t/stop-trace-at-query-fail-point/740/3 "2019-05-29T20:39:08Z")
Thanks and understood. If I come up with something I’ll post here.