[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-xorg-devel
Subject: Testing impedance layer
From: Check Nyah <check.nyah () gmail ! com>
Date: 2014-08-29 18:22:47
Message-ID: CA+W8M+_rvYxQ=HQ6nDFpS6y+7v3FxByrsaO7Mxm+6Mh-7aqwjA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello,
I am testing the impedance layer for the Xserver and I've been running xts
and valgrind on the xserver for the past two days, and i've received alot
of errors. As for the Valgrind Errors <http://paste.kde.org/plbai4or6>, the
main problem results from the fact that the following functions( LogVWrite
(log.c:292), ErrorF (log.c:652), _damageRegionAppend (damage.c:266)
_damageDamageBox (damage.c:386) damagePolyFillRect , (damage.c:1259)
miPaintWindow (miexpose.c:642), miWindowExposures (miexpose.c:471)
KdXVWindowExposures (kxv.c:1012) MapWindow (window.c:2626), have uninitialized
variables, while trying to initialize some of them I was getting serious
compilation errors and I realized that there were other similar variables
which were not initialized at the point of declaration. As for the xts
tests, I even got a segmentation fault <http://paste.kde.org/pfzo6mx2f> on
the Xephyr, which I"m using the backtrace to solve.
In order to test the impedance layer, here is my current plan.
First and foremost, when i resolve the segmentation fault above, I want to
focus exclusively on the xts/xproto test suite which focuses on the
Xserver protocol and hence the Impedance layer, then after fixing the
errors, I'll move to the xts/xiproto tests, when I finish this guess the
impedance layer should be complete.
I'll continue with separating core aspects of the objects, between the
protocol layers and driver layers while running the appropriate test suites
to check and fix errors. I'll like to know if this plan is ok? or is there
anything I'm missing.
I've ran the xts/Xproto test <http://paste.kde.org/pka59dwdf> and I'm
currently interpreting the results to fix the problems, I'll like to know
what to do in test cases where the output is unresolved, as for the failed
test which occurred for the MapWindow, setModifierMapping, I'll like to the
various test cases which run directly against the impedance layer.
Cheers!
Nyah
[Attachment #5 (text/html)]
<div dir="ltr"><div><div>Hello,<br><br></div>I am testing the impedance layer for the \
Xserver and I've been running xts and valgrind on the xserver for the past two \
days, and i've received alot of errors. As for the <a \
href="http://paste.kde.org/plbai4or6" target="_blank">Valgrind Errors</a>, the main \
problem results from the fact that the following functions<span \
style="color:rgb(230,145,56)">(<span style="background-color:rgb(0,255,255)"> \
LogVWrite (log.c:292), ErrorF (log.c:652), _damageRegionAppend (damage.c:266) \
_damageDamageBox (damage.c:386) damagePolyFillRect , (damage.c:1259) miPaintWindow \
(miexpose.c:642), miWindowExposures (miexpose.c:471) KdXVWindowExposures \
(kxv.c:1012) MapWindow (window.c:2626)</span>,</span> have <span \
style="background-color:rgb(230,145,56)"><span></span></span>uninitialized \
variables, while trying to initialize some of them I was getting serious compilation \
errors and I realized that there were other similar variables which were not \
initialized at the point of declaration. As for the xts tests, I even got a <a \
href="http://paste.kde.org/pfzo6mx2f" target="_blank">segmentation fault</a> on the \
Xephyr, which I"m using the backtrace to solve.<br><br></div>In order to test \
the impedance layer, here is my current plan.<br> <div><br>First
and foremost, when i resolve the segmentation fault above, I want to
focus exclusively on the xts/xproto test suite which focuses on the
Xserver protocol and hence the Impedance layer, then after fixing the
errors, I'll move to the xts/xiproto tests, when I finish this guess the
impedance layer should be complete.<br>
<br>I'll continue with separating core aspects of the objects,
between the protocol layers and driver layers while running the
appropriate test suites to check and fix errors. I'll like to know if
this plan is ok? or is there anything I'm missing.<br><br></div><div>I've ran \
the <a href="http://paste.kde.org/pka59dwdf">xts/Xproto test</a> and I'm \
currently interpreting the results to fix the problems, I'll like to know what to \
do in test cases where the output is unresolved, as for the failed test which \
occurred for the MapWindow, setModifierMapping, I'll like to the various test \
cases which run directly against the impedance layer.<br> </div><div>
<br>Cheers!<div class=""><div id=":2ez" class="" tabindex="0"><img class="" \
src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif">Nyah</div></div><br></div></div>
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic