- About
- Downloads
- Blogs and news
- Community
- Support
- Documentation
- Hardware Specification - PRMs
- 2020-2021 INTEL(R) PROCESSORS BASED ON THE "TIGER LAKE" PLATFORM
- 2020 Intel(r) Processors with Hybrid Technology based on the Lakefield platform
- 2020 Discrete GPU formerly named "DG1"
- 2019 Intel(r) processors based on Ice Lake platform
- 2018-2019 Intel(r) processors based on Whiskey Lake platform
- 2017-2019 Intel(r) processors based on Amber Lake platform
- 2017-2019 Intel(r) processors based on Coffee Lake platform
- 2019-2020 Intel(r) processors based on Comet Lake platform
- 2016 Intel(r) processors based Kaby Lake platform
- 2016 Intel(R) Processors Based on Apollo Lake Platform (Broxton Graphics)
- 2015-2016 Intel Processors based on Skylake Platform
- 2014 Intel Processors based on the Bay Trail Platform
- 2014-2015 Intel Processors based on Cherry Trail / Braswell Platform
- 2014-2015 Intel Processors based on Broadwell Platform
- 2013 Intel Core Processor Family
- 2012 Intel Core Processor Family
- Code Documentation
- Source Code
- Build Guide
- 2011 Intel Core Processor Family
- 2010 Intel Core Processor Family
- Bugs and Debugging
- Intel® G45 Express Chipset
- Intel® 965 Express Chipset Family and Intel® G35 Express Chipset Graphics Controller PRM
- Intel® Integrated Graphics Device - OpRegion Specification
- Archived documentation
X server crash when using XtrkCad on Linux Mint 17.1
18 posts / 0 new

Starter
01 Staff (not verified)
01 Staff (not verified)
Jan 17, 2015 - 03:52am
Ok. your other option then is to copy the script and alter the actual xtrcad invocation in it from:
/some/path/to/real/xtrcad --and --some --options
to:
gdb --args /some/path/to/real/xtrcad --and --some --options
Then run the modified scriptin a terminal (gnome-terminal, konsole, xterm, rxvt, whatever)
Then at the gdb prompt: run
And when it crashes: bt (or bt full)
Unfortunately this option does not work.
I created the script, ran it, at the gdb promp entered run. XtrkCad was started, I opened the file, it crashed. When it crashes, I am thrown back at the login screen. So there is no gdb prompt anymore. I logged in with another user account in another terminal and checked the running processes. No gdb...
Ah, of course, silly me - it's Xorg that's crashing, not xtrcad: Switch to a non-X console and attach to Xorg there:
~# gdb -p $(pgrep Xorg)
(gdb) cont
Continuing.
Then switch back to X and trigger the crash. Once it dies, switch back to the console and see if
you have a useful backtrace there. If you don't, you're still missing debug symbols but I don't
know where else you'd find them: Your best bet will be to chase it up with your distro's bug tracking
system.
I tried two sequences:
- ~# gdb --args $XTRKCADLIB/xtrkcad
- (gdb) run
- switch to non-X console
- ~# gdb -p $(pgrep Xorg)
- (gdb) cont
Gdb says Continuing, and then the system freezes. Only way out it via the alt-sysrq-s,u,b route.
- ~# gdb --args $XTRKCADLIB/xtrkcad
- switch to non-X console
- ~# gdb -p $(pgrep Xorg)
- (gdb) cont
Gdb says Continuing, but before I can switch back to the X terminal to enter the run command in gdb, the system freezes again.
Don't bother tracing xtrcad for now - if it's actually X that's crashing, that's the interesting one.
Oops, sorry.
With or without the cont command, starting gdb -p $(pgrep Xorg) in a non-X terminal leads to a freeze when I try to switch to the X-terminal.
Bah, that is annoying. I'll have to consult with some colleagues who are more
familiar with xorg and see what they say.
There are some extra tips here on debugging X crashes:
http://www.x.org/wiki/Development/Documentation/ServerDebugging/
which should help with getting an actual backtrace out.