[Ubuntu-x-swat] [Bug 415357]

2012-02-22 Thread Simon Schubert
Created attachment 57155 reorder Bresenham error correction to avoid overshoot. When fbBresSolid draws a line, it can happen that after the last pixel, the Bresenham error term overflows, and fbBresSolid paints another pixel before adjusting the error term. However, if this happens on the last pi

[Ubuntu-x-swat] [Bug 416421]

2012-02-22 Thread Simon Schubert
Created attachment 57155 reorder Bresenham error correction to avoid overshoot. When fbBresSolid draws a line, it can happen that after the last pixel, the Bresenham error term overflows, and fbBresSolid paints another pixel before adjusting the error term. However, if this happens on the last pi

[Ubuntu-x-swat] [Bug 415357]

2012-01-26 Thread Simon Schubert
Ah. I believe this is the problem, or at least very closely related: : if (clip2 != 0 || drawLast) len++; in combination with these variables: new_x1 = 36 new_x2 = 0 new_y1 = 16

[Ubuntu-x-swat] [Bug 415357]

2012-01-26 Thread Simon Schubert
Ok, I see what is going on there. The len++ is to make the end coordinates inclusive, which they should be if drawLast is set, or if we clipped the end. Now, we changed the end coordinates, but we keep the Bresenham error terms, because we want the same angle (I suppose). However, if we look at

[Ubuntu-x-swat] [Bug 415357]

2012-01-26 Thread Simon Schubert
Just a follow-up to say that solution (d) seems to work for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some application

[Ubuntu-x-swat] [Bug 415357]

2012-01-26 Thread Simon Schubert
The problem seems to be that there are negative coordinates being passed in to ProcPolySegment: (gdb) p/x *(xSegment*)&((xPolySegmentReq *)0x2918e1c)[1] $11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x} I don't know who is supposed to catch this

[Ubuntu-x-swat] [Bug 415357]

2012-01-26 Thread Simon Schubert
Created attachment 56113 gdb backtrace gdb backtrace of the bug. dst is out of bounds. I can provide core file and binaries if required. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/415

[Ubuntu-x-swat] [Bug 416421]

2012-01-26 Thread Simon Schubert
Just a follow-up to say that solution (d) seems to work for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using

[Ubuntu-x-swat] [Bug 416421]

2012-01-26 Thread Simon Schubert
Ok, I see what is going on there. The len++ is to make the end coordinates inclusive, which they should be if drawLast is set, or if we clipped the end. Now, we changed the end coordinates, but we keep the Bresenham error terms, because we want the same angle (I suppose). However, if we look at

[Ubuntu-x-swat] [Bug 416421]

2012-01-26 Thread Simon Schubert
Ah. I believe this is the problem, or at least very closely related: : if (clip2 != 0 || drawLast) len++; in combination with these variables: new_x1 = 36 new_x2 = 0 new_y1 = 16

[Ubuntu-x-swat] [Bug 416421]

2012-01-26 Thread Simon Schubert
The problem seems to be that there are negative coordinates being passed in to ProcPolySegment: (gdb) p/x *(xSegment*)&((xPolySegmentReq *)0x2918e1c)[1] $11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x} I don't know who is supposed to catch this

[Ubuntu-x-swat] [Bug 416421]

2012-01-26 Thread Simon Schubert
Created attachment 56113 gdb backtrace gdb backtrace of the bug. dst is out of bounds. I can provide core file and binaries if required. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad

[Ubuntu-x-swat] [Bug 415357]

2012-01-24 Thread Simon Schubert
I experience a related bug when using KiCad: [ 2507.868] Backtrace: [ 2507.868] 0: /usr/bin/X (xorg_backtrace+0x26) [0x566a86] [ 2507.868] 1: /usr/bin/X (0x40+0x16a6e9) [0x56a6e9] [ 2507.868] 2: /lib/libpthread.so.0 (0x7fa9d12c8000+0xf8a0) [0x7fa9d12d78a0] [ 2507.868] 3: /usr/lib/xorg/mo

[Ubuntu-x-swat] [Bug 416421]

2012-01-24 Thread Simon Schubert
I experience a related bug when using KiCad: [ 2507.868] Backtrace: [ 2507.868] 0: /usr/bin/X (xorg_backtrace+0x26) [0x566a86] [ 2507.868] 1: /usr/bin/X (0x40+0x16a6e9) [0x56a6e9] [ 2507.868] 2: /lib/libpthread.so.0 (0x7fa9d12c8000+0xf8a0) [0x7fa9d12d78a0] [ 2507.868] 3: /usr/lib/xorg/mo