On 01/08/10 09:37, Tom Cowell wrote: >> >> FYI, the error in the log on launchpad was a segfault (SIGSEGV), so >> you appear to have two different errors. The segfault (signal 11) >> should be fixable. The mysterious SIGTERM might be tough to handle >> since it could come from anywhere. >> > > Indeed. Some of the debugger traces (the earlier ones, on the whole) > have SIGTERM, and some have SIGSEGV. What I have proposed is > (probably) only any use for the SIGTERM cases. > > Cheers > Tom > _______________________________________________ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg >
gripes!! valgrind breaks with libc 2.11.90(I'll see later on this), In your case what does valgrind output's say when the crash occurs? Justin P. mattock _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
