Re: [yocto] Debugging question

[Gary Thomas]

On 2017-01-16 11:40, Burton, Ross wrote:


On 16 January 2017 at 04:29, Gary Thomas > wrote:

* Any ideas how upgrading the X server now calls into openssl?
   I've bisected this error down to the change in the X server
   recipe to v1.19 from v1.18.4


$ grep ssl *
xserver-xorg.inc:XORG_CRYPTO ??= "openssl"
xserver-xorg.inc:PACKAGECONFIG[openssl] = "--with-sha1=libcrypto,,openssl"

The X server took the reasonable approach of refusing to reimplement 
cryptographic functions and instead relies on an
external library, of which openssl (well, libcrypto, part of openssl) is one 
option.


Thanks, I missed that.

That said, this wasn't really related to the problem anyway.
libcrypt causes that illegal instruction - on purpose - to
check for certain hardware capabilities and handles it.  Just
running 'continue' in GDB lets the X server get a lot further.

I was able to isolate the problem down to a data structure being
trashed.  I'm not sure yet how/why, but I think there may have
been some important changes that the i.MX6 Vivante hardware
driver isn't currently up to speed on.  Still investigating.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Debugging question

[Burton, Ross]

On 16 January 2017 at 04:29, Gary Thomas  wrote:

> * Any ideas how upgrading the X server now calls into openssl?
>I've bisected this error down to the change in the X server
>recipe to v1.19 from v1.18.4
>

$ grep ssl *
xserver-xorg.inc:XORG_CRYPTO ??= "openssl"
xserver-xorg.inc:PACKAGECONFIG[openssl] = "--with-sha1=libcrypto,,openssl"

The X server took the reasonable approach of refusing to reimplement
cryptographic functions and instead relies on an external library, of which
openssl (well, libcrypto, part of openssl) is one option.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto