Bug 100799 - Segfault libpthread on Debian
Summary: Segfault libpthread on Debian
Status: RESOLVED DUPLICATE of bug 100721
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-26 14:45 UTC by Arie Miller
Modified: 2017-04-28 06:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log trimmed to roughly first 1000 lines. (91.75 KB, text/plain)
2017-04-27 18:55 UTC, Arie Miller
no flags Details

Description Arie Miller 2017-04-26 14:45:51 UTC
[233525.084] (EE) 
[233525.084] (EE) Backtrace:
[233525.084] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x5586924cd46a]
[233525.084] (EE) 1: /usr/lib/xorg/Xorg (0x558692314000+0x1bd219) [0x5586924d1219]
[233525.084] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1ecfcc2000+0x110c0) [0x7f1ecfcd30c0]
[233525.084] (EE) 3: /usr/lib/xorg/Xorg (0x558692314000+0xe6f4f) [0x5586923faf4f]
[233525.084] (EE) 4: /usr/lib/xorg/Xorg (0x558692314000+0x545e5) [0x5586923685e5]
[233525.084] (EE) 5: /usr/lib/xorg/Xorg (0x558692314000+0x58568) [0x55869236c568]
[233525.084] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f1ecf9442b1]
[233525.084] (EE) 7: /usr/lib/xorg/Xorg (_start+0x2a) [0x55869235621a]
[233525.084] (EE) 
[233525.084] (EE) Segmentation fault at address 0x800000016
[233525.084] (EE) 
Fatal server error:
[233525.084] (EE) Caught signal 11 (Segmentation fault). Server aborting
[233525.084] (EE) 
[233525.084] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[233525.084] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[233525.084] (EE) 
[233525.084] (II) AIGLX: Suspending AIGLX clients for VT switch
[233525.132] (EE) Server terminated with error (1). Closing log file.
Comment 1 Michel Dänzer 2017-04-27 00:39:42 UTC
This is not enough information to do anything about the problem. We need at least a backtrace with debugging symbols available for /usr/lib/xorg/Xorg, ideally captured with gdb.
Comment 2 Michel Dänzer 2017-04-27 00:40:10 UTC
Also please attach the full Xorg log file.
Comment 3 Arie Miller 2017-04-27 06:54:15 UTC
(In reply to Michel Dänzer from comment #2)
> Also please attach the full Xorg log file.

This file is huge, the latest one is 1.6GB and the latest old one with a crash is 756Mb.

(In reply to Michel Dänzer from comment #1)
> This is not enough information to do anything about the problem. We need at
> least a backtrace with debugging symbols available for /usr/lib/xorg/Xorg,
> ideally captured with gdb.

It seems the xserver-xorg-core-dbg package isn't available on my release I'll have to look up how to build it.
Comment 4 Michel Dänzer 2017-04-27 07:08:29 UTC
(In reply to renari from comment #3)
> (In reply to Michel Dänzer from comment #2)
> > Also please attach the full Xorg log file.
> 
> This file is huge, the latest one is 1.6GB and the latest old one with a
> crash is 756Mb.

Attach the first 100K or so then.

(Why does it grow that large though? Sounds like something's wrong)


> It seems the xserver-xorg-core-dbg package isn't available on my release

Debugging symbol packages are now auto-generated and available in a separate repository. Add

deb http://debug.mirrors.debian.org/debian-debug/ <suite>-debug main #contrib non-free

to /etc/apt/sources.list(.d/*) and install xserver-xorg-core-dbgsym.
Comment 5 Arie Miller 2017-04-27 18:55:30 UTC
Created attachment 131103 [details]
Xorg.0.log trimmed to roughly first 1000 lines.
Comment 6 Arie Miller 2017-04-27 20:33:35 UTC
Thread 1 "Xorg" received signal SIGPIPE, Broken pipe.
0x00007feefb484cfd in writev () at ../sysdeps/unix/syscall-template.S:84
84      ../sysdeps/unix/syscall-template.S: No such file or directory.


This is one issue that popped up, this didn't terminate the xsession though.
Comment 7 Michel Dänzer 2017-04-28 01:25:21 UTC
Yeah, SIGPIPE is normal during X server operation. Run

 handle SIGPIPE nostop noprint

at the gdb prompt to have it ignore SIGPIPE.

Once gdb stops for SIGSEGV, run

 bt full

and attach the output of that.
Comment 8 Arie Miller 2017-04-28 05:18:53 UTC
Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
ProcXFixesGetCursorImageAndName (client=0x5579051bbe90)
    at ../../../../xfixes/cursor.c:510
510     ../../../../xfixes/cursor.c: No such file or directory.


bt full:
#0  ProcXFixesGetCursorImageAndName (client=0x5579051bbe90)
    at ../../../../xfixes/cursor.c:510
        rep = <optimized out>
        pCursor = 0x5579df0bb110
        image = <optimized out>
        npixels = <optimized out>
        name = <optimized out>
        width = <optimized out>
        height = <optimized out>
        rc = 0
        x = 449
        y = 40
#1  0x00005577f95955e5 in Dispatch () at ../../../../dix/dispatch.c:479
        result = <optimized out>
        start_tick = 12452280
#2  0x00005577f9599568 in dix_main (argc=10, argv=0x7ffec2a1bcc8,
    envp=<optimized out>) at ../../../../dix/main.c:287
        i = <optimized out>
        alwaysCheckForInput = {0, 1}
#3  0x00007feefb3c42b1 in __libc_start_main (main=0x5577f95831e0 <main>,
    argc=10, argv=0x7ffec2a1bcc8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7ffec2a1bcb8)
    at ../csu/libc-start.c:291
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 259158344007019244,
                93973772775920, 140732163800256, 0, 0, 6236008318421035756,
                6245001459393358572}, mask_was_saved = 0}}, priv = {pad = {
              0x0, 0x0, 0x7ffec2a1bd20, 0x7feefdb4c168}, data = {prev = 0x0,
              cleanup = 0x0, canceltype = -1029587680}}}
        not_first_call = <optimized out>
#4  0x00005577f958321a in _start ()
No symbol table info available.
Comment 9 Michel Dänzer 2017-04-28 06:18:10 UTC

*** This bug has been marked as a duplicate of bug 100721 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.