fied to indicate this, sorry.
> Also what could be the possible reasons that xserver is showing
> segmentation fault while running MEM_RW macro??
You should have listed a disas around EIP register
(i.e. info reg, disas $eip-0x40 $eip+0x40 or some such).
That way one would be able to gather
high levels of compatibility?
("relatively" since I know that some udev / syscalls stuff has been
deprecated sometimes...)
- so, given an incompatibility, using/creating an ld wrapper library
workaround is not an option?
Andreas Mohr
--
GNU/Linux. It&#x
Xorg.0.log file content for specifics of all the specific
problem areas mentioned above, and more.
So far, *not* very specific help, but it might just end up helping anyway :)
HTH,
Andreas Mohr
___
xorg@lists.x.org: X.Org support
Archives: http:/
ess the actions I mentioned
mainly serve to figure out the separation of
whether it is a setup-/environment-related weirdness, or
whether it is a driver implementation/configuration issue in fact.
HTH,
Andreas Mohr
___
xorg@lists.x.org: X.Org support
Arc
to failure
due to their inherent wear and tear - movement, thermo-related etc.).
Nice to hear that this seems nailed now.
Andreas Mohr
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
