Steve Kostecke wrote:
> Michel =?ISO-8859-1?Q?D=E4nzer?= said:
>
>
>> On Mon, 2009-02-16 at 19:55 -0500, Steve Kostecke wrote:
>>
>>
>>> Program received signal SIGPIPE, Broken pipe.
>>>
>> SIGPIPE is normal when a client dies without cleanly terminating its X
>> connection. You can
Michel =?ISO-8859-1?Q?D=E4nzer?= said:
>On Mon, 2009-02-16 at 19:55 -0500, Steve Kostecke wrote:
>
>> Program received signal SIGPIPE, Broken pipe.
>
>SIGPIPE is normal when a client dies without cleanly terminating its X
>connection. You can tell gdb to ignore SIGPIPE with
>
>handle SIGPIPE nosto
Brice Goglin said:
>Could you catch a debugging backtrace with gdb (through ssh) after
>installing libpixman-1-0-dbg and xserver-xorg-core-dbg?
I've been able to collect backtraces from a number of X lockups (and am
able to tell Xorg to continue via gdb) using the GCC-4.1 libpixman.
The back tra
On Mon, 2009-02-16 at 19:55 -0500, Steve Kostecke wrote:
>
> Program received signal SIGPIPE, Broken pipe.
SIGPIPE is normal when a client dies without cleanly terminating its X
connection. You can tell gdb to ignore SIGPIPE with
handle SIGPIPE nostop
--
Earthling Michel Dänzer |
Brice Goglin said:
>Could you catch a debugging backtrace with gdb (through ssh) after
>installing libpixman-1-0-dbg and xserver-xorg-core-dbg?
I had a couple of total lockups within 30 minutes of switching back to
the uptream libpixman. I couldn't anything at all out of gdb.
I switched back to
Brice Goglin said:
>Could you catch a debugging backtrace with gdb (through ssh) after
>installing libpixman-1-0-dbg and xserver-xorg-core-dbg?
Sorry for the delay.
I had found a libpixman crash related bug report which claimed that
using GCC-4.1 to compile libpixman solved the problem. In my ca
Steve Kostecke wrote:
> Backtrace:
> 0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x48dd0a]
> 1: /lib/libc.so.6 [0x2b241c5c6f60]
> 2: /usr/lib/libpixman-1.so.0 [0x2b241b8ab79a]
> 3: /usr/lib/libpixman-1.so.0(pixman_image_composite+0x70f) [0x2b241b89c64f]
> 4: /usr/lib/xorg/modules//libfb.so(fbComposite+
Package: xserver-xorg
Version: 1:7.3+18
Severity: important
I am experiencing repeated random X crashes / lockups on an AMD64 system
(ASUS M3A-H + AMD Phenom 9600 Quad-Core CPU). I've included
/proc/cpuinfo at the end of this report. This bug may be related to
the problem I reported in bug # 51388
8 matches
Mail list logo
