On 2010/01/25 21:55, Chris Bennett wrote: > Owain Ainsworth wrote: > >On Mon, Jan 25, 2010 at 07:52:14AM -0600, Chris Bennett wrote: > >>I have now had this happen exactly the same on two different days > >> > >>Using scrotwm, latest -current running dual head > >> > >>Running at same time: thunderbird, firefox, xterm > >> > >>Upon writing a file in kate, immediate fail back to console. > >>File was successfully written this time, corrupted last time. > > > >So X probably crashed. going to need more information than that. > > > >Please get a copy of the xenocara source tree, and read README in the > >xenocara folder. After that, use that information to rebuild your X > >server and the video driver in question with debug symbols and then get > >a backtrace from gdb. > > > >-0- > > I got quick crash. > > Got scrotwm.core
It looks like X probably crashed first, you'll need to follow oga's instructions to get a usable backtrace from that. > #0 0x1c007cba in ?? () > (gdb) bt > #0 0x1c007cba in ?? () > #1 0x83f71de0 in ?? () > #2 0x00000000 in ?? () Looks like no debug symbols. In general for something in ports, if you want a usable backtrace you need to do something like this first: make clean && make DEBUG='-g' INSTALL_STRIP='' repackage reinstall (not every port honours INSTALL_STRIP/DEBUG, though they should, and many do). Sometimes you also want -O0 to disable the optimizer, it can give a clearer backtrace, but it affects the generated code (and might prevent the crash..) But this is very likely due to the X server crashing first. So spend the time following xenocara/README first.
