Xorg crashes...

[Tom Cowell]

I was responding to this remark from Peter Hutterer:

>> uhm. SIGTERM is the termination signal. Something's shutting down your
>> server.

If SIGTERM is coming from another process, then the debugger won't
provide any information about _which_ process. However, a recursive
strace of startx (and all its children and grandchildren) _might_
identify the source of the signal. Even if the X Server is killing
itself with SIGTERM, that would be worth knowing.

However, if it stays up for days before crashing, strace might
generate an unacceptable amount of output.

Cheers
Tom


2010/1/8 Ryan Daly <daly at ctc.com>:
> On 01/08/2010 03:50 AM, Tom Cowell wrote:
>> I'm a novice here - excuse me butting int, and ignore me if this isn't useful.
>>
>> If I understand correctly, you have:
>>
>> a) The X Server receives SIGTERM and exits.
>> b) The source of the SIGTERM is unknown (but perhaps one of the
>> clients of the X Server).
>> c) You can reproduce this by starting X and the console command line.
>>
>> What about tracing all of this with strace? e.g.:
>>
>> strace -fo <suitable_log_file_name> startx
>>
>> This will generate a vast amount of output, including the part where
>> the X Server receives SIGTERM and exists. Hopefully, a little bit
>> before this, you might see another process sending the SIGTERM with
>> kill().
>
> No, no.  Thanks for the input.
>
> I've run Xorg under a debugger and it has produced some backtraces.  I'm
> not sure if running strace would produce anything beyond what gdb is
> already providing.  I could be wrong, though.
> --
>
> ------------------------------------------------------------
> This message and any files transmitted within are intended
> solely for the addressee or its representative and may
> contain company sensitive information.  If you are not the
> intended recipient, notify the sender immediately and delete
> this message.  Publication, reproduction, forwarding, or
> content disclosure is prohibited without the consent of the
> original sender and may be unlawful.
>
> Concurrent Technologies Corporation and its Affiliates.
> www.ctc.com  1-800-282-4392
> ------------------------------------------------------------
>